| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, "Wood, Dan" <hexpert(at)amazon(dot)com> |
| Subject: | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Date: | 2017-09-28 22:24:47 |
| Message-ID: | CAH2-Wzn5U+jE1yuQO9e1o+m=VkO47iEQWx042ra0WyLehtu+Pg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Sep 28, 2017 at 3:20 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Sep 28, 2017 at 5:47 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>> In the end, commit 6bfa88a fixed that old recovery bug by making sure
>> the recovery routine heap_xlog_lock() did the right thing. In both
>> cases (Feb 2014 and today), the index wasn't really corrupt -- it just
>> pointed to the root of a HOT chain when it should point to some child
>> tuple (or maybe a successor HOT chain).
>
> Unless I'm very confused, it's really not OK to point at a child tuple
> rather than the root of the HOT chain.
Please see my later clarification.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-09-29 06:04:12 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Robert Haas | 2017-09-28 22:20:51 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-28 22:39:03 | Re: Minor codegen silliness in ExecInterpExpr() |
| Previous Message | Robert Haas | 2017-09-28 22:20:51 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |