Search Results - Hackorum

Topic	Mailing Lists	Activity	Participants
documentation build log is busted, and has been for awhile documentation build log is busted, and has been for awhile Tom LanePeter Eisentraut 6 replies Jun 28, 2010	docs	6 replies Jun 28, 2010	5 Tom Lane Bruce Momjian Dave Page Stefan Kaltenbrunner Peter Eisentraut
fillfactor gets set to zero for toast tables fillfactor gets set to zero for toast tables Tom LaneITAGAKI Takahiro 9 replies Jun 04, 2010	hackers	9 replies Jun 04, 2010	3 ITAGAKI Takahiro Tom Lane Alvaro Herrera
pgsql: Fix misuse of Lossy Counting (LC) algorithm in pgsql: Fix misuse of Lossy Counting (LC) algorithm in Tom LaneTom Lane 0 replies May 30, 2010	comitters	0 replies May 30, 2010	1 Tom Lane
pgsql: Fix misuse of Lossy Counting (LC) algorithm in pgsql: Fix misuse of Lossy Counting (LC) algorithm in Tom LaneTom Lane 0 replies May 30, 2010	comitters	0 replies May 30, 2010	1 Tom Lane
pgsql: Change the notation for calling functions with named parameters pgsql: Change the notation for calling functions with named parameters Tom LaneTom Lane 0 replies May 30, 2010	comitters	0 replies May 30, 2010	1 Tom Lane
Performance problem in textanycat/anytextcat Performance problem in textanycat/anytextcat Tom LaneTom Lane 21 replies May 29, 2010	hackers	21 replies May 29, 2010	4 Tom Lane Robert Haas Jaime Casanova Heikki Linnakangas
pgsql: Add text to "Populating a Database" pointing out that bulk data pgsql: Add text to "Populating a Database" pointing out that bulk data Tom LaneTom Lane 0 replies May 29, 2010	comitters	0 replies May 29, 2010	1 Tom Lane
Clearing psql's input buffer after auto-reconnect Clearing psql's input buffer after auto-reconnect Tom LaneBruce Momjian 2 replies May 28, 2010	hackers	2 replies May 28, 2010	3 Tom Lane Greg Sabino Mullane Bruce Momjian
pgsql: Abort a FETCH_COUNT-controlled query if we observe any I/O error pgsql: Abort a FETCH_COUNT-controlled query if we observe any I/O error Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Fix oversight in the previous patch that made LIKE throw error pgsql: Fix oversight in the previous patch that made LIKE throw error Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Rewrite LIKE's %-followed-by-_ optimization so it really works pgsql: Rewrite LIKE's %-followed-by-_ optimization so it really works Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Rewrite LIKE's %-followed-by-_ optimization so it really works pgsql: Rewrite LIKE's %-followed-by-_ optimization so it really works Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Rewrite LIKE's %-followed-by-_ optimization so it really works pgsql: Rewrite LIKE's %-followed-by-_ optimization so it really works Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Rejigger mergejoin logic so that a tuple with a null in the first pgsql: Rejigger mergejoin logic so that a tuple with a null in the first Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Rejigger mergejoin logic so that a tuple with a null in the first pgsql: Rejigger mergejoin logic so that a tuple with a null in the first Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Rejigger mergejoin logic so that a tuple with a null in the first pgsql: Rejigger mergejoin logic so that a tuple with a null in the first Tom LaneTom Lane 0 replies May 28, 2010	comitters	0 replies May 28, 2010	1 Tom Lane
pgsql: Change ps_status.c to explicitly track the current logical length pgsql: Change ps_status.c to explicitly track the current logical length Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane
pgsql: Change ps_status.c to explicitly track the current logical length pgsql: Change ps_status.c to explicitly track the current logical length Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane
pgsql: Change ps_status.c to explicitly track the current logical length pgsql: Change ps_status.c to explicitly track the current logical length Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane
pgsql: Change ps_status.c to explicitly track the current logical length pgsql: Change ps_status.c to explicitly track the current logical length Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane
pgsql: Change ps_status.c to explicitly track the current logical length pgsql: Change ps_status.c to explicitly track the current logical length Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane
pgsql: Change ps_status.c to explicitly track the current logical length pgsql: Change ps_status.c to explicitly track the current logical length Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane
9.0beta2 release plans 9.0beta2 release plans Tom LaneSimon Riggs 1 reply May 27, 2010	hackers	1 reply May 27, 2010	2 Tom Lane Simon Riggs
pgsql: Fix the volatility marking of textanycat() and anytextcat(): they pgsql: Fix the volatility marking of textanycat() and anytextcat(): they Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane
pgsql: Make CREATE INDEX run expression preprocessing on a proposed pgsql: Make CREATE INDEX run expression preprocessing on a proposed Tom LaneTom Lane 0 replies May 27, 2010	comitters	0 replies May 27, 2010	1 Tom Lane

Loading more results...

Mailing Lists

Saved searches