Re: [GENERAL] REASSIGN OWNED simply doesn't work

2017-10-16 Thread Alvaro Herrera
David G. Johnston wrote: > ​You could at least fix the documentation bug since this superuser-only > restriction doesn't show up and is in fact contradicted by the sentence > ​"REASSIGN OWNED requires privileges on both the source role(s) and the > target role." The error message that comes back

Re: [GENERAL] REASSIGN OWNED simply doesn't work

2017-10-16 Thread Sam Gendler
I wasn't under the impression that open source meant "totally unsupported, undocumented, and fix it yourself if it's broken." If your attitude is going to be "it's good enough for my needs so I'll just rudely dismiss any problems with it," why merge it at all? And for what it is worth, postgresql

Re: [GENERAL] REASSIGN OWNED simply doesn't work

2017-10-13 Thread David G. Johnston
On Fri, Oct 13, 2017 at 6:04 AM, Alvaro Herrera wrote: > Sam Gendler wrote: > > psql 9.6.3 on OS X. > > > > I'm dealing with a production database in which all db access has been > made > > by the same user - the db owner, which isn't actually a superuser because > > the

Re: [GENERAL] REASSIGN OWNED simply doesn't work

2017-10-13 Thread Alvaro Herrera
Sam Gendler wrote: > psql 9.6.3 on OS X. > > I'm dealing with a production database in which all db access has been made > by the same user - the db owner, which isn't actually a superuser because > the db runs on amazon RDS - amazon retains the superuser privilege for its > own users and makes

Re: [GENERAL] REASSIGN OWNED simply doesn't work

2017-10-12 Thread Stephen Cook
On 2017-10-12 21:09, Sam Gendler wrote: > psql 9.6.3 on OS X. > > I'm dealing with a production database in which all db access has been > made by the same user - the db owner, which isn't actually a superuser > because the db runs on amazon RDS - amazon retains the superuser > privilege for its