| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Adding -E switch to pg_dumpall |
| Date: | 2017-07-14 10:39:16 |
| Message-ID: | CAB7nPqQcYWmrm2n-dVaMUhYPKFU_DxQwPuUGuC4ZF+8B=dS5xQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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/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?
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2017-07-14 11:04:18 | Re: More flexible LDAP auth search filters? |
| Previous Message | Marina Polyakova | 2017-07-14 10:36:02 | Re: WIP Patch: Pgbench Serialization and deadlock errors |