Re: postgres_fdw: dead lock in a same transaction when postgres_fdw server is lookback

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Xiaoran Wang <wxiaoran(at)vmware(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: postgres_fdw: dead lock in a same transaction when postgres_fdw server is lookback
Date: 2022-10-01 14:38:52
Message-ID: 833d34af6e094e0271a618f9af5c1997ad632e3e.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 2022-10-01 at 04:02 +0000, Xiaoran Wang wrote:
> I created a postgers_fdw server lookback as the test does. Then run the following SQLs
>
> [create a foreign server via loopback and manipulate the same data locally and via foreign table]
>
> Then the transaction got stuck. Should the "lookback" server be disabled in the postgres_fdw?

It shouldn't; there are good use cases for that ("autonomous transactions").
AT most, some cautioning documentation could be added, but I am not convinced
that even that is necessary.

I'd say that this is a pretty obvious case of pilot error.

Yours,
Laurenz Albe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-10-01 16:14:20 Re: longfin and tamandua aren't too happy but I'm not sure why
Previous Message Peter Eisentraut 2022-10-01 12:07:29 Re: ICU for global collation