Search Results - Hackorum

Topic	Mailing Lists	Activity	Participants
WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows WITH RECURSIVE ... CYCLE in vanilla SQL: issues with arrays of rows Tom LaneBruce Momjian 13 replies Jan 08, 2009	hackers	13 replies Jan 08, 2009	4 Tom Lane Alvaro Herrera David Fetter Bruce Momjian
CLUSTER, REINDEX, VACUUM in "read only" transaction? CLUSTER, REINDEX, VACUUM in "read only" transaction? Tom LaneSimon Riggs 5 replies Oct 15, 2008	hackers	5 replies Oct 15, 2008	3 Tom Lane Simon Riggs Peter Eisentraut
pgsql: Fix COPY documentation to not imply that HEADER can be used pgsql: Fix COPY documentation to not imply that HEADER can be used Tom LaneTom Lane 0 replies Oct 10, 2008	comitters	0 replies Oct 10, 2008	1 Tom Lane
pgsql: Fix COPY documentation to not imply that HEADER can be used pgsql: Fix COPY documentation to not imply that HEADER can be used Tom LaneTom Lane 0 replies Oct 10, 2008	comitters	0 replies Oct 10, 2008	1 Tom Lane
pgsql: Fix COPY documentation to not imply that HEADER can be used pgsql: Fix COPY documentation to not imply that HEADER can be used Tom LaneTom Lane 0 replies Oct 10, 2008	comitters	0 replies Oct 10, 2008	1 Tom Lane
pgsql: Fix COPY documentation to not imply that HEADER can be used pgsql: Fix COPY documentation to not imply that HEADER can be used Tom LaneTom Lane 0 replies Oct 10, 2008	comitters	0 replies Oct 10, 2008	1 Tom Lane
pgsql: Fix small query-lifespan memory leak introduced by 8.4 change in pgsql: Fix small query-lifespan memory leak introduced by 8.4 change in Tom LaneTom Lane 0 replies Oct 10, 2008	comitters	0 replies Oct 10, 2008	1 Tom Lane
pgsql: Fix omission of DiscardStmt in GetCommandLogLevel, per report pgsql: Fix omission of DiscardStmt in GetCommandLogLevel, per report Tom LaneTom Lane 0 replies Oct 10, 2008	comitters	0 replies Oct 10, 2008	1 Tom Lane
pgsql: Fix omission of DiscardStmt in GetCommandLogLevel, per report pgsql: Fix omission of DiscardStmt in GetCommandLogLevel, per report Tom LaneTom Lane 0 replies Oct 10, 2008	comitters	0 replies Oct 10, 2008	1 Tom Lane
CREATE DATABASE vs delayed table unlink CREATE DATABASE vs delayed table unlink Tom LaneMatthew Wakeling 9 replies Oct 10, 2008	hackers	9 replies Oct 10, 2008	2 Tom Lane Heikki Linnakangas
pgsql: Un-break non-NLS builds. pgsql: Un-break non-NLS builds. Tom LaneAlvaro Herrera 1 reply Oct 09, 2008	hackerscomitters	1 reply Oct 09, 2008	2 Tom Lane Alvaro Herrera
pgsql: Improve the recently-added code for inlining set-returning pgsql: Improve the recently-added code for inlining set-returning Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must pgsql: Fix overly tense optimization of PLpgSQL_func_hashkey: we must Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
pgsql: Fix crash in bytea-to-XML mapping when the source value is pgsql: Fix crash in bytea-to-XML mapping when the source value is Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
pgsql: Fix crash in bytea-to-XML mapping when the source value is pgsql: Fix crash in bytea-to-XML mapping when the source value is Tom LaneTom Lane 0 replies Oct 09, 2008	comitters	0 replies Oct 09, 2008	1 Tom Lane
Better error message for a small problem with WITH RECURSIVE Better error message for a small problem with WITH RECURSIVE Tom LaneTom Lane 4 replies Oct 08, 2008	hackers	4 replies Oct 08, 2008	3 Tom Lane Bruce Momjian Heikki Linnakangas
Shouldn't pg_settings.enumvals be array of text? Shouldn't pg_settings.enumvals be array of text? Tom LaneGreg Smith 16 replies Oct 08, 2008	hackers	16 replies Oct 08, 2008	4 Greg Smith Tom Lane Magnus Hagander Alvaro Herrera
pgsql: Modify the parser's error reporting to include a specific hint pgsql: Modify the parser's error reporting to include a specific hint Tom LaneTom Lane 0 replies Oct 08, 2008	comitters	0 replies Oct 08, 2008	1 Tom Lane
pgsql: Improve some of the comments in fsmpage.c. pgsql: Improve some of the comments in fsmpage.c. Tom LaneTom Lane 0 replies Oct 07, 2008	comitters	0 replies Oct 07, 2008	1 Tom Lane
pgsql: Extend CTE patch to support recursive UNION (ie, without ALL). pgsql: Extend CTE patch to support recursive UNION (ie, without ALL). Tom LaneTom Lane 0 replies Oct 07, 2008	comitters	0 replies Oct 07, 2008	1 Tom Lane
pgsql: Improve parser error location for cases where an INSERT or UPDATE pgsql: Improve parser error location for cases where an INSERT or UPDATE Tom LaneTom Lane 0 replies Oct 07, 2008	comitters	0 replies Oct 07, 2008	1 Tom Lane

Loading more results...

Mailing Lists

Saved searches