Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function - Mailing list pgsql-hackers

From Kirk Wolak
Subject Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function
Date
Msg-id CACLU5mS64HcLpk+Kg=7y8gvZZk5MSZF-hSqSWX=YnT3bpUbjUA@mail.gmail.com
Whole thread Raw
In response to Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function
List 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 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Let's make PostgreSQL multi-threaded
Next
From: Jacob Champion
Date:
Subject: Re: Docs: Encourage strong server verification with SCRAM