| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| 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-03 14:57:12 |
| Message-ID: | 20160503145712.GJ10850@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Craig Ringer (craig(at)2ndquadrant(dot)com) wrote:
> On 3 May 2016 at 19:04, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> wrote:
>
> > With commit a9f0e8e5a2e779a888988cb64479a6723f668c84, now pg_dump, use a
> > bitmap
> > to represent what to include. With this commit if non-super user is unable
> > to perform the dump.
> >
>
> Hm. I think we need a src/bin/pg_dump/t/ test for the TAP suite for this
> one, because something this fundamental should really have blown the
> buildfarm up when committed.
I'm in the process of building a pretty comprehensive set, as discussed
in another thread.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-05-03 15:04:17 | Re: pgindent fixups |
| Previous Message | Robert Haas | 2016-05-03 14:51:04 | Re: Need help debugging why autovacuum seems "stuck" -- until I use superuser to vacuum freeze pg_database |