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

From: Kirk Wolak <wolakk(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function
Date: 2023-06-05 15:18:54
Message-ID: CACLU5mS64HcLpk+Kg=7y8gvZZk5MSZF-hSqSWX=YnT3bpUbjUA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jun 4, 2023 at 1:41 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Kirk Wolak <wolakk(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2023-06-05 15:22:01 Re: Docs: Encourage strong server verification with SCRAM
Previous Message Tom Lane 2023-06-05 15:18:27 Re: Let's make PostgreSQL multi-threaded