Re: pg_dumpall storing multiple copies of DB's? - Mailing list pgsql-general

From Bill McGonigle
Subject Re: pg_dumpall storing multiple copies of DB's?
Date
Msg-id 521C3A76-305C-11D6-9492-003065EAE3C0@medicalmedia.com
Whole thread Raw
In response to Re: pg_dumpall storing multiple copies of DB's?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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).


pgsql-general by date:

Previous
From: "Trewern, Ben"
Date:
Subject: Re: Mandrake RPMs uploaded
Next
From: Vince Vielhaber
Date:
Subject: Re: storing intermediate results in recursive plpgsql