| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PageIsAllVisible()'s trustworthiness in Hot Standby |
| Date: | 2012-12-14 20:45:42 |
| Message-ID: | CA+Tgmoa=9twuTokXs9hFwCbR51GMeMKfX4ikNKJJa5CxSzYScw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 12, 2012 at 12:31 PM, Pavan Deolasee
<pavan(dot)deolasee(at)gmail(dot)com> wrote:
> On Wed, Dec 12, 2012 at 1:35 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Tue, Dec 4, 2012 at 12:10 PM, Pavan Deolasee
>> <pavan(dot)deolasee(at)gmail(dot)com> wrote:
>>> Hmm. Yeah, I do not have guts to prove that either. I'll probably write up a
>>> comment for your consideration to explain why we don't trust PD_ALL_VISIBLE
>>> in Hot standby for seq scans, but still trust VM for index-only scans.
>>
>> Sure.
>>
>
> Here is a small patch that adds comments to heap scan code explaining
> why we don't trust the all-visible flag in the page, still continue to
> support index-only scans on hot standby.
Committed, with a few modifications to the last part.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2012-12-14 20:46:19 | Re: Use of systable_beginscan_ordered in event trigger patch |
| Previous Message | Robert Haas | 2012-12-14 20:39:44 | Re: Re: bulk_multi_insert infinite loops with large rows and small fill factors |