Re: pg_dump/restore encoding woes - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_dump/restore encoding woes
Date
Msg-id 521CBFDE.5080508@dunslane.net
Whole thread Raw
In response to Re: pg_dump/restore encoding woes  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: pg_dump/restore encoding woes  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
On 08/27/2013 10:36 AM, Heikki Linnakangas wrote:
> 0001-Divorce-pg_dump-E-option-from-PGCLIENTENCODING.patch
>
> Separates pg_dump -E from PGCLIENTENCODING.
>
>


Wouldn't it be better to do this another way? Separating these two will 
be confusing, to say the least, as well as inconsistent with what os 
done elsewhere. Why not provide a new option that specifically allows a 
client encoding that only applies during the query phase?

cheers

andrew



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Properly initialize negative/empty cache entries in relfilenodemap
Next
From: Heikki Linnakangas
Date:
Subject: Re: pg_dump/restore encoding woes