| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: fix schema ownership on first connection preliminary |
| Date: | 2004-08-02 01:58:48 |
| Message-ID: | 410D9FD8.8040208@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> I'm also wondering about what side-effects this will have on pg_dump
> behavior. In particular, will pg_dump try to "ALTER OWNER public",
> and if so will that be appropriate? We haven't previously needed to
> assume that we are restoring into a database with the same datowner as
> we dumped from...
In my batch of pg_dump patches that have gone in, pg_dump will now do
exactly that. The reason was so that if someone altered the owner of
their public schema, it should be dumped like that.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-08-02 02:17:46 | dumping large object comments |
| Previous Message | Christopher Kings-Lynne | 2004-08-02 01:52:12 | SQL conformance docs |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-08-02 03:40:01 | Re: Fix for OWNER TO breaking ACLs |
| Previous Message | Tom Lane | 2004-08-02 01:32:08 | Re: fix for parameterized queries in DECLARE CURSOR statements |