From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Add isolationtester spec for old heapam.c bug |
Date: | 2016-02-29 18:08:42 |
Message-ID: | 17574.1456769322@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> guaibasaurus is not a particularly slow machine, and it's not using any
>> special build flags AFAICT. So I'm not sure what to make of this case,
>> except that it proves the timing problem can manifest on normal builds.
> Hmm, I suppose I could fix this by using three different advisory locks
> rather than a single one. (My assumption is that the timing dependency
> is the order in which the backends are awakened when the advisory lock
> is released.) I would release the locks one by one rather than all
> together.
Sounds plausible. You would probably need several seconds' pg_sleep() in
between the lock releases to ensure that even on slow/overloaded machines,
there's enough time for all wakened backends to do what they're supposed
to do.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-02-29 19:36:03 | pgsql: Make new isolationtester test more stable |
Previous Message | Alvaro Herrera | 2016-02-29 17:44:06 | Re: pgsql: Add isolationtester spec for old heapam.c bug |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-02-29 18:30:23 | Re: pg_dump / copy bugs with "big lines" ? |
Previous Message | Julien Rouhaud | 2016-02-29 18:04:58 | Re: Publish autovacuum informations |