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

Поиск
Список
Период
Сортировка
От Morris de Oryx
Тема Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function
Дата
Msg-id CAKqncchB20egnRq5GgHquM54U5EqPyzq7usFjjABa08ouEZp_g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function  (Kirk Wolak <wolakk@gmail.com>)
Список 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 

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Kirk Wolak
Дата:
Сообщение: RFC: Adding \history [options] [filename] to psql (Snippets and Shared Queries)
Следующее
От: vignesh C
Дата:
Сообщение: Re: Implement generalized sub routine find_in_log for tap test