| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | 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-10-01 01:25:30 |
| Message-ID: | CAH2-WznUkrH4mxdwXhASb3-i1zAt69AsBWftn-m0-1k-dp13Jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Sep 28, 2017 at 1:20 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Maybe what this means is that we need to do both Dan's initially
> proposed patch (or something related to it) apart from the fixes already
> pushed. IOW we need to put back some of the "tupkeep" business ...
I took the time to specifically check if that would fix the problem.
Unfortunately, it did not. We see exactly the same problem, or at
least amcheck/REINDEX produces exactly the same error. I checked both
Dan's original update_freeze.patch, and your revision that retained
some of the "tupkeep" stuff,
0002-Don-t-freeze-recently-dead-HOT-tuples, which you posted on
September 6th.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2017-10-01 02:28:39 | Re: pgsql: Add test for postmaster crash restarts. |
| Previous Message | Andres Freund | 2017-09-30 22:44:24 | Re: pgsql: Add test for postmaster crash restarts. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2017-10-01 02:28:39 | Re: pgsql: Add test for postmaster crash restarts. |
| Previous Message | Andres Freund | 2017-09-30 22:44:24 | Re: pgsql: Add test for postmaster crash restarts. |