Re: pg_dumpall default database

From: "Albe Laurenz" <all(at)adv(dot)magwien(dot)gv(dot)at>
To: "Dave Page *EXTERN*" <dpage(at)postgresql(dot)org>, "Neil Conway" <neilc(at)samurai(dot)com>
Cc: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pg_dumpall default database
Date: 2007-01-16 07:37:00
Message-ID: 52EF20B2E3209443BC37736D00C3C1380C4AEDCF@EXADV1.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Dave Page wrote:
>> I agree with Peter: specifying the database name as implemented seems
>> like it would be prone to confusion.
>
> OK, updated patch attached. This has
>
> -E <dbname> or --default-database=<dbname>

Ouch. This calls for confusion with the -E flag of pg_dump,
which means 'encoding'. Something else might be better.

It would be nice to be able to specify the encoding for
pg_dumpall, though, rather than having to set PG_CLIENTENCODING.

Yours,
Laurenz Albe

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2007-01-16 09:09:46 Re: O_DIRECT support for Windows
Previous Message Pavel Stehule 2007-01-16 06:52:37 Re: scrollable cursor sup. for SPI