Re: pg_dump/restore encoding woes

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump/restore encoding woes
Date: 2013-08-27 15:03:58
Message-ID: 521CBFDE.5080508@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-08-27 15:14:24 Re: pg_dump/restore encoding woes
Previous Message Andres Freund 2013-08-27 14:46:18 Properly initialize negative/empty cache entries in relfilenodemap