| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump issue with renamed system schemas |
| Date: | 2020-04-10 20:26:45 |
| Message-ID: | 32073.1586550405@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Bossart, Nathan" <bossartn(at)amazon(dot)com> writes:
> I think I've found a small bug in pg_dump that could cause some schema
> privileges to be missed. In short, if you've renamed a schema that
> has an entry in pg_init_privs, pg_dump will skip dumping the initial
> ACL for the schema. This results in missing privileges on restore.
This seems like a special case of the issue discussed in
AFAICT we didn't think we'd found a satisfactory solution yet.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-04-10 20:29:39 | Re: [HACKERS] make async slave to wait for lsn to be replayed |
| Previous Message | Tom Lane | 2020-04-10 20:22:09 | Re: spin_delay() for ARM |