Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
- From: Bruce Momjian <bruce(at)momjian(dot)us>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Neil Conway <neilc(at)samurai(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, "Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
- Date: Wed, 30 Jan 2008 21:15:35 -0500 (EST)
Tom Lane wrote: > Bruce Momjian <bruce(at)momjian(dot)us> writes: > > Another question --- why don't we just turn off synchronized_seqscans > > when we do COPY TO? That would fix pg_dump and be transparent. > > Enforcing this from the server side seems a pretty bad idea. Note that > there were squawks about having pg_dump behave this way at all; if the > control is on the pg_dump side then at least we have the chance to make > it a user option later. > > Also, you forgot about pg_dump -d. OK, but keep in mind if we use synchronized_seqscans in pg_dump we will have to recognize that GUC forever. -- Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
- Follow-Ups:
- References:
- Prev by Date: Re: [PATCHES] Better default_statistics_target
- Next by Date: Re: Oops - BF:Mastodon just died
- Previous by thread: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
- Next by thread: Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable
- Indexes: