| From: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 18:23:38 |
| Message-ID: | 50A2902A.1020209@archidevsys.co.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14/11/12 04:32, Merlin Moncure wrote:
> 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
>
>
How about displaying a warning, when people try to use the 'feature', as
well as document it?
Cheers,
Gavin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-11-13 18:43:34 | Re: Inadequate thought about buffer locking during hot standby replay |
| Previous Message | Tom Lane | 2012-11-13 18:16:11 | Re: Proposal for Allow postgresql.conf values to be changed via SQL |