| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Trewern, Ben" <Ben(dot)Trewern(at)mowlem(dot)com> |
| Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Updating pg_attribute - Permission denied |
| Date: | 2000-10-23 14:01:50 |
| Message-ID: | 8110.972309710@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Trewern, Ben" <Ben(dot)Trewern(at)mowlem(dot)com> writes:
> Looks like I have turned off usecatupd in pg_shadow. Doh! Was mucking
> around with permissions some time ago but not had any trouble up till now.
> Any ideas how to switch it back? Update pg_shadow SET usecatupd ..... gives
> me Permission denied!!!
Catch-22, ain't it? I think the only workaround at the moment is to
create a new user with superuser privileges (who will have usecatupd
true), become him, and fix your own usecatupd via UPDATE. Then you
can discard the new superuser identity.
A cleaner solution would be to have an ALTER USER variant that allows
setting/clearing usecatupd. Item for TODO list ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-23 14:17:03 | Re: blobs dont rollback ? |
| Previous Message | Tom Lane | 2000-10-23 13:54:52 | Re: Weird effects using BLOBs from libpq |