Re: pg_dump handling of ALTER DEFAULT PRIVILEGES IN SCHEMA

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump handling of ALTER DEFAULT PRIVILEGES IN SCHEMA
Date: 2021-10-22 20:14:33
Message-ID: 8E38D1C7-4298-4543-99A4-382F7BA9D4C1@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/5/21, 11:33 PM, "Bossart, Nathan" <bossartn(at)amazon(dot)com> wrote:
> Attached is an attempt at cleaning the patch up and adding an
> informative comment and a test case.

For future reference, there was another thread for this bug [0], and a
fix was committed [1].

Nathan

[0] https://postgr.es/m/CAA3qoJnr2%2B1dVJObNtfec%3DqW4Z0nz%3DA9%2Br5bZKoTSy5RDjskMw%40mail.gmail.com
[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=2acc84c

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2021-10-22 20:16:54 Re: add retry mechanism for achieving recovery target before emitting FATA error "recovery ended before configured recovery target was reached"
Previous Message Bossart, Nathan 2021-10-22 20:08:01 Re: Inconsistent behavior of pg_dump/pg_restore on DEFAULT PRIVILEGES