| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Fuhr <mike(at)fuhr(dot)org> |
| Cc: | Gary Doades <gpd(at)gpdnet(dot)co(dot)uk>, pgsql-bugs(at)postgresql(dot)org, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Subject: | Re: Permissions problem with sequences |
| Date: | 2004-09-05 16:21:58 |
| Message-ID: | 29206.1094401318@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> There is, however, an ownership problem with restoring sequences
> in 8.0.0beta. In 7.4.5, for example, pg_dump issues a SET SESSION
> AUTHORIZATION command and then creates a table, so implicitly-created
> sequences are restored with the correct ownership. In 8.0.0beta2,
> however, pg_dump doesn't issue SET SESSION AUTHORIZATION but rather
> creates a table and then issues ALTER TABLE ... OWNER TO.
Yeah, we still need to find a solution for that. I'd prefer not to
back out the ALTER OWNER TO changes, but I will if nothing else
presents itself.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-09-05 16:44:33 | Re: readline selection (was Re: [GENERAL] psql leaking? - SOLVED) |
| Previous Message | Ivan-Sun1 | 2004-09-05 11:25:02 | plpgsql error handling bug |