| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. |
| Date: | 2016-02-11 14:36:00 |
| Message-ID: | CA+TgmoYh2UycJAaW+UONuXJhThyRD_Eq_1xDbivROLLYaSfb2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Feb 11, 2016 at 9:29 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <rhaas(at)postgresql(dot)org> writes:
>> Add some isolation tests for deadlock detection and resolution.
>
> Buildfarm says this needs work ...
>
> dromedary is one of mine, do you need me to look into what is
> happening?
That would be great. Taking a look at what happened, I have a feeling
this may be a race condition of some kind in the isolation tester. It
seems to have failed to recognize that a1 started waiting, and that
caused the "deadlock detected" message to reported differently. I'm
not immediately sure what to do about that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-02-11 14:48:39 | Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution. |
| Previous Message | Tom Lane | 2016-02-11 14:29:56 | Re: pgsql: Add some isolation tests for deadlock detection and resolution. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-02-11 14:38:40 | Re: Invalid user-level setting = confusing error message |
| Previous Message | Robert Haas | 2016-02-11 14:32:52 | Re: Speed up Clog Access by increasing CLOG buffers |