Re: Inadequate thought about buffer locking during hot standby replay - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Inadequate thought about buffer locking during hot standby replay
Date
Msg-id CA+TgmoZ3dHfqTp2xbXjx6Fxhfu-kv6vn=NB-5mvYk_gN_MyCiA@mail.gmail.com
Whole thread Raw
In response to Re: Inadequate thought about buffer locking during hot standby replay  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On Tue, Nov 13, 2012 at 10:32 AM, Merlin Moncure <mmoncure@gmail.com> wrote:
> On Tue, Nov 13, 2012 at 9:03 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Ok. It won't help all that much on 9.0, though.
>>
>> Well, it won't help GIST much, but the actually-reported-from-the-field
>> case is in btree, and it does fix that.
>>
>> It occurs to me that if we're sufficiently scared of this case, we could
>> probably hack the planner (in 9.0 only) to refuse to use GIST indexes
>> in hot-standby queries.  That cure might be worse than the disease though.
>
> if anything, it should be documented.  if you do this kind of thing
> people will stop installing bugfix releases.

Agreed.  I think doing that in a back-branch release would be
extremely user-hostile.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: Inadequate thought about buffer locking during hot standby replay
Next
From: Robert Haas
Date:
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL