| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump broken for non-super user |
| Date: | 2016-05-04 12:49:33 |
| Message-ID: | CA+TgmoZfo50tgP+6g4k5hZ8hAzvKtzJ-LXieFhe6aqbqwGkF_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 4, 2016 at 5:29 AM, Stephen Frost <sfrost(at)snowman(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stas Kelvich | 2016-05-04 12:58:00 | tsvector filter problem |
| Previous Message | Peter Eisentraut | 2016-05-04 12:23:38 | Re: psql :: support for \ev viewname and \sv viewname |