| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(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(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable |
| Date: | 2008-01-31 01:41:20 |
| Message-ID: | 28144.1201743680@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2008-01-31 02:13:37 | Re: [PATCHES] Better default_statistics_target |
| Previous Message | Bruce Momjian | 2008-01-31 01:38:31 | Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2008-01-31 02:13:37 | Re: [PATCHES] Better default_statistics_target |
| Previous Message | Bruce Momjian | 2008-01-31 01:38:31 | Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable |