From: | Bill McGonigle <mcgonigle(at)medicalmedia(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dumpall storing multiple copies of DB's? |
Date: | 2002-03-05 17:13:32 |
Message-ID: | 521C3A76-305C-11D6-9492-003065EAE3C0@medicalmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tuesday, March 5, 2002, at 12:09 , Tom Lane wrote:
>> The current system, which only has one pg_shadow entry for the
>> database's datdba, is still producing the dumps with multiple copies.
>> When I run:
>> SELECT datname, coalesce(usename, (select usename from pg_shadow where
>> usesysid=(select datdba from pg_database where datname='template0'))),
>> pg_encoding_to_char(d.encoding), datistemplate, datpath FROM
>> pg_database
>> d LEFT JOIN pg_shadow u ON (datdba = usesysid) WHERE datallowconn;
>> (from pg_dumpall) I only see one copy of the database.
>
> Most curious. What exactly do you see from that query? I'm wondering
> if pg_dumpall's simplistic parsing of the output ("while read ...") is
> getting fooled by embedded spaces or some such.
>
> regards, tom lane
>
Sending a copy of output off-list, since I'm security paranoid (the
archives, not the membership).
From | Date | Subject | |
---|---|---|---|
Next Message | fhallais | 2002-03-05 17:16:45 | Need help changing NAMEDATALEN |
Previous Message | Trewern, Ben | 2002-03-05 17:11:02 | Re: Mandrake RPMs uploaded |