From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Steve Wampler <swampler(at)noao(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump in 7.2.4 with trigger functions |
Date: | 2005-01-31 17:58:17 |
Message-ID: | 21011.1107194297@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Steve Wampler <swampler(at)noao(dot)edu> writes:
> In fact, now that I look more at the dump file, it's kinda interesting.
> Near the top are the lines:
> \connect "atst.logdb" atst
> SET client_encoding = 'SQL_ASCII';
> SET check_function_bodies = false;
> SET SESSION AUTHORIZATION 'sbw';
> ('sbw' is a superuser, 'atst' was not. The restore was run by
> [Linux] user 'sbw'.)
Yeah, this is a bug in pg_dump --- it's failing to consider that doing
the \connect that way might lose superuser privileges. More recent
versions of pg_dump avoid that problem, but as long as you're on 7.4
the best advice may be to not rely on the -C switch.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Edward Macnaghten | 2005-01-31 18:12:21 | Re: Identity Problem |
Previous Message | Guy Rouillier | 2005-01-31 17:32:57 | Re: Postgresql and Athlon64 ? |