Search Results - Hackorum

Topic	Mailing Lists	Activity	Participants
A thought: should we run pgindent now? A thought: should we run pgindent now? Tom LaneJaime Casanova 28 replies Feb 26, 2010	hackers	28 replies Feb 26, 2010	+6 9 Bruce Momjian Robert Haas Tom Lane Andrew Dunstan Magnus Hagander Heikki Linnakangas Alvaro Herrera Jaime Casanova Greg Smith
pgsql: Clean up handling of XactReadOnly and RecoveryInProgress checks. pgsql: Clean up handling of XactReadOnly and RecoveryInProgress checks. Tom LaneTom Lane 0 replies Feb 20, 2010	comitters	0 replies Feb 20, 2010	1 Tom Lane
pgsql: Reduce the rescan cost estimate for Materialize nodes to pgsql: Reduce the rescan cost estimate for Materialize nodes to Tom LaneTom Lane 0 replies Feb 19, 2010	comitters	0 replies Feb 19, 2010	1 Tom Lane
pgsql: Volatile-ize all five places where we expect a PG_TRY block to pgsql: Volatile-ize all five places where we expect a PG_TRY block to Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Volatile-ize all five places where we expect a PG_TRY block to pgsql: Volatile-ize all five places where we expect a PG_TRY block to Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Volatile-ize all five places where we expect a PG_TRY block to pgsql: Volatile-ize all five places where we expect a PG_TRY block to Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Volatile-ize all five places where we expect a PG_TRY block to pgsql: Volatile-ize all five places where we expect a PG_TRY block to Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Volatile-ize all five places where we expect a PG_TRY block to pgsql: Volatile-ize all five places where we expect a PG_TRY block to Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Volatile-ize all five places where we expect a PG_TRY block to pgsql: Volatile-ize all five places where we expect a PG_TRY block to Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Provide some rather hokey ways for EXPLAIN to print FieldStore pgsql: Provide some rather hokey ways for EXPLAIN to print FieldStore Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Provide some rather hokey ways for EXPLAIN to print FieldStore pgsql: Provide some rather hokey ways for EXPLAIN to print FieldStore Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Fix ExecEvalArrayRef to pass down the old value of the array pgsql: Fix ExecEvalArrayRef to pass down the old value of the array Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Fix ExecEvalArrayRef to pass down the old value of the array pgsql: Fix ExecEvalArrayRef to pass down the old value of the array Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Fix ExecEvalArrayRef to pass down the old value of the array pgsql: Fix ExecEvalArrayRef to pass down the old value of the array Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Force READY portals into FAILED state when a transaction or pgsql: Force READY portals into FAILED state when a transaction or Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Force READY portals into FAILED state when a transaction or pgsql: Force READY portals into FAILED state when a transaction or Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
Large object dumps vs older pg_restore Large object dumps vs older pg_restore Tom LaneKaiGai Kohei 3 replies Feb 18, 2010	hackers	3 replies Feb 18, 2010	3 KaiGai Kohei Tom Lane Andrew Dunstan
pgsql: Fix up pg_dump's treatment of large object ownership and ACLs. pgsql: Fix up pg_dump's treatment of large object ownership and ACLs. Tom LaneTom Lane 0 replies Feb 18, 2010	comitters	0 replies Feb 18, 2010	1 Tom Lane
pgsql: Stamp HEAD as 9.0devel, and update various places that were pgsql: Stamp HEAD as 9.0devel, and update various places that were Tom LaneDavid Fetter 3 replies Feb 17, 2010	comitters	3 replies Feb 17, 2010	3 Tom Lane Alvaro Herrera David Fetter
pgsql: Take care to reprocess an uncommitted notify message. pgsql: Take care to reprocess an uncommitted notify message. Tom LaneTom Lane 0 replies Feb 17, 2010	comitters	0 replies Feb 17, 2010	1 Tom Lane
pgsql: When updating ShmemVariableCache from a checkpoint record, be pgsql: When updating ShmemVariableCache from a checkpoint record, be Tom LaneTom Lane 0 replies Feb 17, 2010	comitters	0 replies Feb 17, 2010	1 Tom Lane
pgsql: Prevent #option dump from crashing on FORI statement with null pgsql: Prevent #option dump from crashing on FORI statement with null Tom LaneTom Lane 0 replies Feb 17, 2010	comitters	0 replies Feb 17, 2010	1 Tom Lane
pgsql: Prevent #option dump from crashing on FORI statement with null pgsql: Prevent #option dump from crashing on FORI statement with null Tom LaneTom Lane 0 replies Feb 17, 2010	comitters	0 replies Feb 17, 2010	1 Tom Lane
pgsql: Prevent #option dump from crashing on FORI statement with null pgsql: Prevent #option dump from crashing on FORI statement with null Tom LaneTom Lane 0 replies Feb 17, 2010	comitters	0 replies Feb 17, 2010	1 Tom Lane
pgsql: log_error_verbosity is now LOGGING_WHAT category. pgsql: log_error_verbosity is now LOGGING_WHAT category. Tom LaneTom Lane 0 replies Feb 17, 2010	comitters	0 replies Feb 17, 2010	1 Tom Lane

Loading more results...

Mailing Lists

Saved searches