Re: [HACKERS] Adding -E switch to pg_dumpall

2017-09-01 Thread Michael Paquier
On Sat, Sep 2, 2017 at 1:32 AM, Robert Haas wrote: > On Fri, Jul 21, 2017 at 9:21 AM, Michael Paquier > wrote: >> On Thu, Jul 20, 2017 at 11:17 AM, Fabien COELHO wrote: >>> Ok for me. I switched the status to "Ready for

Re: [HACKERS] Adding -E switch to pg_dumpall

2017-09-01 Thread Robert Haas
On Fri, Jul 21, 2017 at 9:21 AM, Michael Paquier wrote: > On Thu, Jul 20, 2017 at 11:17 AM, Fabien COELHO wrote: >> Ok for me. I switched the status to "Ready for committers". > > Thanks for the review, Fabien. LGTM. Committed. -- Robert Haas

Re: [HACKERS] Adding -E switch to pg_dumpall

2017-07-21 Thread Michael Paquier
On Thu, Jul 20, 2017 at 11:17 AM, Fabien COELHO wrote: > Ok for me. I switched the status to "Ready for committers". Thanks for the review, Fabien. -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription:

Re: [HACKERS] Adding -E switch to pg_dumpall

2017-07-20 Thread Fabien COELHO
Hello Michaël-san, Attached is a patch to add support for this switch. I am parking that in the next CF. I'm in favor of this feature for consistency with pg_dump, and as the environment variable workaround is not specially elegant and can induce issues of its own. Patch applies and

Re: [HACKERS] Adding -E switch to pg_dumpall

2017-07-15 Thread Michael Paquier
On Fri, Jul 14, 2017 at 12:39 PM, Michael Paquier 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: >

[HACKERS] Adding -E switch to pg_dumpall

2017-07-14 Thread Michael Paquier
Hi all, 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/75e4c42d37e6a74e9fb57c2e9f1300d601070...@tiger.nexperience.com Now it is possible to enforce the encoding