| From: | "Gevik Babakhani" <pgdev(at)xs4all(dot)nl> |
|---|---|
| To: | "'Gregory Stark'" <stark(at)enterprisedb(dot)com>, "'Jonah H(dot) Harris'" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Proposed patch: synchronized_scanning GUC variable |
| Date: | 2008-01-27 23:09:51 |
| Message-ID: | 000601c86139$bc5b2860$0a01a8c0@gevmus |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> >> Per today's -hackers discussion, add a GUC variable to
> allow clients
> >> to disable the new synchronized-scanning behavior, and
> make pg_dump
> >> disable sync scans so that it will reliably preserve row
> ordering.
> >> This is a pretty trivial patch, but seeing how late we are
> in the 8.3
> >> release cycle, I thought I'd better post it for comment anyway.
> >
> > +1
>
> I liked the "synchronized_sequential_scans" idea myself.
>
> But otherwise, sure.
>
this will save some hackwork I have to do for a import/export project I am
doing.
+1, please
Regards,
Gevik Babakhani
------------------------------------------------
PostgreSQL NL http://www.postgresql.nl
TrueSoftware BV http://www.truesoftware.nl
------------------------------------------------
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-28 00:00:41 | GSSAPI doesn't play nice with non-canonical host names |
| Previous Message | Gregory Stark | 2008-01-27 21:54:58 | Re: Proposed patch: synchronized_scanning GUC variable |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-01-28 00:37:42 | Re: Proposed patch: synchronized_scanning GUC variable |
| Previous Message | Gregory Stark | 2008-01-27 21:54:58 | Re: Proposed patch: synchronized_scanning GUC variable |