Search Results - Hackorum

Topic	Mailing Lists	Activity	Participants
Transient plans versus the SPI API Transient plans versus the SPI API Tom LaneSimon Riggs 29 replies Aug 19, 2011	hackers	29 replies Aug 19, 2011	+6 9 Tom Lane Dimitri Fontaine Simon Riggs Robert Haas Jeff Davis Hannu Krosing Kevin Grittner Peter Eisentraut Bruce Momjian
Yes, WaitLatch is vulnerable to weak-memory-ordering bugs Yes, WaitLatch is vulnerable to weak-memory-ordering bugs Tom LaneHeikki Linnakangas 5 replies Aug 08, 2011	hackers	5 replies Aug 08, 2011	4 Tom Lane Robert Haas Peter Geoghegan Heikki Linnakangas
pgsql: Clean up ill-advised attempt to invent a private set of Node tag pgsql: Clean up ill-advised attempt to invent a private set of Node tag Tom LaneTom Lane 0 replies Aug 06, 2011	comitters	0 replies Aug 06, 2011	1 Tom Lane
pgsql: Clean up ill-advised attempt to invent a private set of Node tag pgsql: Clean up ill-advised attempt to invent a private set of Node tag Tom LaneTom Lane 0 replies Aug 06, 2011	comitters	0 replies Aug 06, 2011	1 Tom Lane
pgsql: Fix thinko in documentation of local_preload_libraries. pgsql: Fix thinko in documentation of local_preload_libraries. Tom LaneTom Lane 0 replies Aug 06, 2011	comitters	0 replies Aug 06, 2011	1 Tom Lane
pgsql: Fix thinko in documentation of local_preload_libraries. pgsql: Fix thinko in documentation of local_preload_libraries. Tom LaneTom Lane 0 replies Aug 06, 2011	comitters	0 replies Aug 06, 2011	1 Tom Lane
pgsql: Fix thinko in documentation of local_preload_libraries. pgsql: Fix thinko in documentation of local_preload_libraries. Tom LaneTom Lane 0 replies Aug 06, 2011	comitters	0 replies Aug 06, 2011	1 Tom Lane
pgsql: Reduce PG_SYSLOG_LIMIT to 900 bytes. pgsql: Reduce PG_SYSLOG_LIMIT to 900 bytes. Tom LaneTom Lane 0 replies Aug 06, 2011	comitters	0 replies Aug 06, 2011	1 Tom Lane
pgsql: Reduce PG_SYSLOG_LIMIT to 900 bytes. pgsql: Reduce PG_SYSLOG_LIMIT to 900 bytes. Tom LaneTom Lane 0 replies Aug 06, 2011	comitters	0 replies Aug 06, 2011	1 Tom Lane
pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait Tom LaneSimon Riggs 3 replies Aug 02, 2011	comitters	3 replies Aug 02, 2011	2 Tom Lane Simon Riggs
pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place. pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place. Tom LaneTom Lane 0 replies Aug 02, 2011	comitters	0 replies Aug 02, 2011	1 Tom Lane
pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place. pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place. Tom LaneTom Lane 0 replies Aug 02, 2011	comitters	0 replies Aug 02, 2011	1 Tom Lane
pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place. pgsql: Move CheckRecoveryConflictDeadlock() call to a safer place. Tom LaneTom Lane 0 replies Aug 02, 2011	comitters	0 replies Aug 02, 2011	1 Tom Lane
pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait Tom LaneTom Lane 0 replies Aug 02, 2011	comitters	0 replies Aug 02, 2011	1 Tom Lane
pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait pgsql: Fix incorrect initialization of ProcGlobal->startupBufferPinWait Tom LaneTom Lane 0 replies Aug 02, 2011	comitters	0 replies Aug 02, 2011	1 Tom Lane
9.1 release schedule 9.1 release schedule Tom LaneTom Lane 0 replies Aug 02, 2011	hackers	0 replies Aug 02, 2011	1 Tom Lane

Mailing Lists

Saved searches