Re: Inadequate thought about buffer locking during hot standby replay

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Inadequate thought about buffer locking during hot standby replay
Date: 2012-11-13 15:32:33
Message-ID: CAHyXU0ww4=wTK34Me4iBbhOPkFVFLKR2DjnXAZ4ZnhXvQFeOuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 13, 2012 at 9:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2012-11-13 16:02:05 Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown
Previous Message Tom Lane 2012-11-13 15:03:59 Re: Inadequate thought about buffer locking during hot standby replay