| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | "Wong, Yi Wen" <yiwong(at)amazon(dot)com>, "Wood, Dan" <hexpert(at)amazon(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
| Date: | 2017-10-08 17:29:06 |
| Message-ID: | CAH2-Wzmfc7pv-WV7aphJrUaOaEo6n_2EBowPdQrjTiMFWOwWdw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sat, Oct 7, 2017 at 4:25 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> Hmm, I think I added a random sleep (max. 100ms) right after the
> HeapTupleSatisfiesVacuum call in vacuumlazy.c (lazy_scan_heap), and that
> makes the race easier to hit.
I still cannot reproduce. Perhaps you can be more specific?
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-10-08 19:25:45 | pgsql: Increase distance between flush requests during bulk file copies |
| Previous Message | Tom Lane | 2017-10-08 16:23:41 | pgsql: Reduce "X = X" to "X IS NOT NULL", if it's easy to do so. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2017-10-08 18:34:36 | Re: search path security issue? |
| Previous Message | Pavel Stehule | 2017-10-08 17:23:59 | Re: is possible cache tupledesc templates in execution plan? significant performance issue, maybe bug? |