Horton

Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function

Kirk Wolak <wolakk@gmail.com>

View thread
From: Kirk Wolak <wolakk@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Imseih (AWS), Sami" <simseih@amazon.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-06-05T15:18:54Z
Lists: pgsql-hackers 
On Sun, Jun 4, 2023 at 1:41 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Kirk Wolak <wolakk@gmail.com> writes:
> .. to strings of other lengths.  So the new output (before 016107478
> fixed it) is
>
> pg_dump: warning: could not resolve dependency loop among these items:
> pg_dump: detail: FUNCTION a_f  (ID 216 OID 40532)
> pg_dump: detail: CONSTRAINT a_pkey  (ID 3466 OID 40531)
> pg_dump: detail: POST-DATA BOUNDARY  (ID 3612)
> pg_dump: detail: TABLE DATA a  (ID 3610 OID 40525)
> pg_dump: detail: PRE-DATA BOUNDARY  (ID 3611)
>
>                         regards, tom lane
>
+1