Re: pg_dump broken for non-super user
От | Robert Haas |
---|---|
Тема | Re: pg_dump broken for non-super user |
Дата | |
Msg-id | CA+TgmoZfo50tgP+6g4k5hZ8hAzvKtzJ-LXieFhe6aqbqwGkF_w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_dump broken for non-super user (Stephen Frost <sfrost@snowman.net>) |
Ответы |
Re: pg_dump broken for non-super user
|
Список | pgsql-hackers |
On Wed, May 4, 2016 at 5:29 AM, Stephen Frost <sfrost@snowman.net> wrote: > There is no such limitation on using pg_dump as a non-superuser. It's > always been the case that you need to be able to LOCK the table that > you're dumping. If you don't have rights to LOCK a certain table then > pg_dump is going to throw an error just like the one you saw. But in Rushabh's example, he's not doing that. He's trying to do a full-database dump of a database that contains one object which the dump user has rights to access. Previously, that worked. Now, it fails with an error about a system catalog. How is that not broken? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: