Search Results - Hackorum

Topic	Mailing Lists	Activity	Participants
"could not reattach to shared memory" captured in buildfarm "could not reattach to shared memory" captured in buildfarm Tom LaneTom Lane 7 replies May 05, 2009	hackers	7 replies May 05, 2009	4 Tom Lane Magnus Hagander Dave Page Alvaro Herrera
pgsql: Fix pg_resetxlog to remove archive status files along with WAL pgsql: Fix pg_resetxlog to remove archive status files along with WAL Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Fix pg_resetxlog to remove archive status files along with WAL pgsql: Fix pg_resetxlog to remove archive status files along with WAL Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Fix pg_resetxlog to remove archive status files along with WAL pgsql: Fix pg_resetxlog to remove archive status files along with WAL Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Fix pg_resetxlog to remove archive status files along with WAL pgsql: Fix pg_resetxlog to remove archive status files along with WAL Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Fix mis-description of XML Schema functions, per discussion. pgsql: Fix mis-description of XML Schema functions, per discussion. Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Fix unintelligible description created by removing only part of a pgsql: Fix unintelligible description created by removing only part of a Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Fix assign_pgstat_temp_directory() to ensure the directory path pgsql: Fix assign_pgstat_temp_directory() to ensure the directory path Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Fix already-obsolete hint message ... pgsql: Fix already-obsolete hint message ... Tom LaneTom Lane 0 replies May 03, 2009	comitters	0 replies May 03, 2009	1 Tom Lane
pgsql: Install some simple defenses in postmaster startup to help ensure pgsql: Install some simple defenses in postmaster startup to help ensure Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: We don't need major_release_split any more. pgsql: We don't need major_release_split any more. Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Split the release notes into a separate file for each (active) pgsql: Split the release notes into a separate file for each (active) Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Split the release notes into a separate file for each (active) pgsql: Split the release notes into a separate file for each (active) Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Split the release notes into a separate file for each (active) pgsql: Split the release notes into a separate file for each (active) Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Split the release notes into a separate file for each (active) pgsql: Split the release notes into a separate file for each (active) Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Split the release notes into a separate file for each (active) pgsql: Split the release notes into a separate file for each (active) Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Split the release notes into a separate file for each (active) pgsql: Split the release notes into a separate file for each (active) Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Fix plpgsql's EXIT so that an EXIT without a label only matches a pgsql: Fix plpgsql's EXIT so that an EXIT without a label only matches a Tom LaneTom Lane 0 replies May 02, 2009	comitters	0 replies May 02, 2009	1 Tom Lane
pgsql: Fix a couple of cases where the plpgsql grammar looked for T_WORD pgsql: Fix a couple of cases where the plpgsql grammar looked for T_WORD Tom LaneTom Lane 0 replies May 01, 2009	comitters	0 replies May 01, 2009	1 Tom Lane
pgsql: When checking for datetime field overflow, we should allow a pgsql: When checking for datetime field overflow, we should allow a Tom LaneTom Lane 0 replies May 01, 2009	comitters	0 replies May 01, 2009	1 Tom Lane
pgsql: When checking for datetime field overflow, we should allow a pgsql: When checking for datetime field overflow, we should allow a Tom LaneTom Lane 0 replies May 01, 2009	comitters	0 replies May 01, 2009	1 Tom Lane
pgsql: When checking for datetime field overflow, we should allow a pgsql: When checking for datetime field overflow, we should allow a Tom LaneTom Lane 0 replies May 01, 2009	comitters	0 replies May 01, 2009	1 Tom Lane
pgsql: When checking for datetime field overflow, we should allow a pgsql: When checking for datetime field overflow, we should allow a Tom LaneTom Lane 0 replies May 01, 2009	comitters	0 replies May 01, 2009	1 Tom Lane
pgsql: When checking for datetime field overflow, we should allow a pgsql: When checking for datetime field overflow, we should allow a Tom LaneTom Lane 0 replies May 01, 2009	comitters	0 replies May 01, 2009	1 Tom Lane
pgsql: When checking for datetime field overflow, we should allow a pgsql: When checking for datetime field overflow, we should allow a Tom LaneTom Lane 0 replies May 01, 2009	comitters	0 replies May 01, 2009	1 Tom Lane

Loading more results...

Mailing Lists

Saved searches