pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: 唯一★ <270246512@qq.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: 回复: 回复: 回复: BUG #16101: tables in the DB is not available after pg_restore
Date: Sun, 17 Nov 2019 14:06:33 -0500
Message-ID: <8347.1574017593@sss.pgh.pa.us> (raw)
In-Reply-To: <20191117173039.ahky34s6emk2zgxx@development>
References: <16101-5a569e5aac6aa84e@postgresql.org>
<20191108111339.xlopjkbwfhxfvwt3@development>
<tencent_5865E10D689BCC05DFD0BC291ED869BEAA05@qq.com>
<20191113133029.kagiy6vjjeoguatp@development>
<tencent_9DD805D110A0A91F987ADEAB25EE2D69BB05@qq.com>
<20191113151803.6ye47vh3vyp5ufah@development>
<tencent_9BBC6D521745C3B6A62D60F2798F96A5B707@qq.com>
<tencent_8F1706C3F7A62AE0C279A4169C37F36D3607@qq.com>
<20191117173039.ahky34s6emk2zgxx@development>
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes:
> What happens is that we *do not* include ACL for the public schema
> unless when running in "clean" mode (i.e. when pg_dump is executed with
> "-c" switch). This is the relevant comment from pg_dump.c:
Note that that bit is new since v11; the OP is complaining about v10
which acted differently.
I did some simple experiments that suggest that things are fine in
this area as of v11+, but the reason we changed it is that it wasn't
fine before. The most likely bet IMO is that the OP did a
dump/restore with -c -x at some point, and that lost the ACL for
the public schema, and now that state will be preserved by
additional dump/restore cycles with -c. It'd be advisable to
drop the database and create it fresh instead of using -c.
regards, tom lane
view thread (8+ messages) latest in thread
Message-ID: <8347.1574017593@sss.pgh.pa.us> Permalink: ../8347.1574017593@sss.pgh.pa.us/ Also on: postgresql.org/message-id/8347.1574017593@sss.pgh.pa.us ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-bugs@postgresql.org Cc: tgl@sss.pgh.pa.us, tomas.vondra@2ndquadrant.com, 270246512@qq.com Subject: Re: 回复: 回复: 回复: BUG #16101: tables in the DB is not available after pg_restore In-Reply-To: <8347.1574017593@sss.pgh.pa.us> References: <16101-5a569e5aac6aa84e@postgresql.org> <20191108111339.xlopjkbwfhxfvwt3@development> <tencent_5865E10D689BCC05DFD0BC291ED869BEAA05@qq.com> <20191113133029.kagiy6vjjeoguatp@development> <tencent_9DD805D110A0A91F987ADEAB25EE2D69BB05@qq.com> <20191113151803.6ye47vh3vyp5ufah@development> <tencent_9BBC6D521745C3B6A62D60F2798F96A5B707@qq.com> <tencent_8F1706C3F7A62AE0C279A4169C37F36D3607@qq.com> <20191117173039.ahky34s6emk2zgxx@development> <8347.1574017593@sss.pgh.pa.us> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox