| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | "Wood, Dan" <hexpert(at)amazon(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "Wong, Yi Wen" <yiwong(at)amazon(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Date: | 2017-10-06 13:18:30 |
| Message-ID: | 20171006131830.ktirfceetnnjwigm@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Wood, Dan wrote:
> Yes, I’ve been testing 9.6. I’ll try Alvaro’s patch today.
>
> I would prefer to focus on either latest 9X or 11dev.
I tested my patch on 9.4 and 9.5 today and it seems to close the problem
(with the patch, I waited 10x as many iterations as it took for the
problem to occur ~10 times without the patch), but I can reproduce a
problem in 9.6 with my patch installed. There must be something new in
9.6 that is causing the problem to reappear.
> Does Alvaro’s patch presume any of the other patch to set COMMITTED in
> the freeze code?
I don't know what you mean. Here is the 9.6 version of my patch. Note
that HEAP_XMIN_FROZEN (which uses the XMIN_COMMITTED bit as I recall)
was introduced in 9.4.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Fix-bugs.patch | text/plain | 5.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-06 13:28:03 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Alvaro Herrera | 2017-10-06 10:57:18 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-06 13:28:03 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Previous Message | Robert Haas | 2017-10-06 13:11:10 | Re: parallel worker (PID ) exited with exit code 1 |