Horton

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

Morris de Oryx <morrisdeoryx@gmail.com>

View thread View on postgr.es
From: Morris de Oryx <morrisdeoryx@gmail.com>
To:
Cc: "Imseih (AWS), Sami" <simseih@amazon.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-06-05T16:03:46Z
Lists: pgsql-hackers 
Another suggestion for AWS/RDS: Expose *all of the logs in the upgrade tool
chain*. If I'd had all of the logs at the start of this, I'd have been able
to track down the issue myself quite quickly. Setting up that simple case
database took me less than an hour today. Without the logs, it's been
impossible (until the RDS patch a month ago) and difficult (now) to get a
sense of what's happening.

Thank you

On Mon, Jun 5, 2023 at 5:19 PM Kirk Wolak <wolakk@gmail.com> wrote:

> 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
>

Commits

  1. Doc: explain about dependency tracking for new-style SQL functions.

  2. Fix pg_dump's failure to honor dependencies of SQL functions.

  3. Fix misuse of pg_log_info() for details/hints.