Re: [HACKERS] Adding -E switch to pg_dumpall - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Adding -E switch to pg_dumpall
Date
Msg-id CAB7nPqSA7OqpTmAGCMHbAGGn8kfsL0dO2HG7eejk5GOL5MNHcg@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Adding -E switch to pg_dumpall  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Adding -E switch to pg_dumpall
List pgsql-hackers
On Fri, Jul 14, 2017 at 12:39 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> While looking at a user problem, I got surprised that pg_dumpall does
> not have a -E switch. This has been discussed a bit in the past like
> here:
> https://www.postgresql.org/message-id/75E4C42D37E6A74E9FB57C2E9F1300D60107073E@tiger.nexperience.com
>
> Now it is possible to enforce the encoding used by using
> PGCLIENTENCODING but I think that a switch would be useful as well,
> particularly for Windows where "set" needs to be used. Are there any
> objections to a patch adding support for that? Such a patch should do:
> - Call PQsetClientEncoding if an encoding is defined after getting a connection.
> - Pass down -E to pg_dump calls if something is set.
>
> Thoughts?

Attached is a patch to add support for this switch. I am parking that
in the next CF.
-- 
Michael

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] hash index on unlogged tables doesn't behave as expected
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] segfault in HEAD when too many nested functions call