| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: sync_seqscans in postgresql.conf |
| Date: | 2011-12-20 13:41:54 |
| Message-ID: | CABUevEy+4rDwXMHOdzC0f8_HrP_a=L162W4m1-9RK1zGo1My7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 20, 2011 at 14:38, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Dec 20, 2011 at 8:35 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Is there any reason why the setting synchronize_seqscans is in the
>> section "version/platform compatibility" in postgresql.conf? Is it
>> just because nobody could find a better place for it? ;) It seems a
>> bit wrong to me...
>
> Presumably the thought was that you would turn it off to restore that
> existed in older versions of PostgreSQL. Doesn't seem much different
> from default_with_oids or lo_compat_privileges.
Seems very different to me - those change *what* happens when you do
certain things. sync_seqscans is just a performance tuning option, no?
It doesn't actually change the semantics of any operations...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ktm@rice.edu | 2011-12-20 13:47:05 | Re: sync_seqscans in postgresql.conf |
| Previous Message | Magnus Hagander | 2011-12-20 13:40:37 | Pause at end of recovery |