From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "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 21:54:58 |
Message-ID: | 87hcgzrl1p.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Jonah H. Harris" <jonah(dot)harris(at)gmail(dot)com> writes:
> On Jan 27, 2008 3:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> 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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
From | Date | Subject | |
---|---|---|---|
Next Message | Gevik Babakhani | 2008-01-27 23:09:51 | Re: Proposed patch: synchronized_scanning GUC variable |
Previous Message | Gevik Babakhani | 2008-01-27 21:04:38 | Re: MSVC Build error |
From | Date | Subject | |
---|---|---|---|
Next Message | Gevik Babakhani | 2008-01-27 23:09:51 | Re: Proposed patch: synchronized_scanning GUC variable |
Previous Message | Jonah H. Harris | 2008-01-27 20:54:59 | Re: Proposed patch: synchronized_scanning GUC variable |