Re: Rare deadlock failure in create_am test

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: Rare deadlock failure in create_am test
Date: 2020-09-04 13:58:35
Message-ID: 872415.1599227915@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> On Fri, Sep 4, 2020 at 2:13 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm inclined to think that the best fix is to put
>>
>> begin;
>> lock table tenk2;
>> ...
>> commit;

> Makes sense, except s/tenk2/fast_emp4000/, no?

Sorry, thinko ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2020-09-04 14:01:23 Re: [PATCH] Redudant initilization
Previous Message Ashutosh Bapat 2020-09-04 13:23:37 Re: Ideas about a better API for postgres_fdw remote estimates