Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers. - Mailing list pgsql-bugs

From Juan José Santamaría Flecha
Subject Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers.
Date
Msg-id CAC+AXB18qKozX6BjPm89=XEh4YJeULO+ATvwpeNt5i0G_+iy=g@mail.gmail.com
Whole thread Raw
In response to Re: pg_dump's "--exclude-table" and "--exclude-table-data" options are ignored and/or cause the dump to fail entirely unless both the schema and table name use 1950s-era identifiers.  (tutiluren@tutanota.com)
List pgsql-bugs

On Wed, Jul 22, 2020 at 5:17 PM <tutiluren@tutanota.com> wrote:
Jul 22, 2020, 9:36 AM by juanjo.santamaria@gmail.com:
I can reproduce a test case in an English_United States.1252 WIndows 10 machine, and the setting "Beta: Use unicode UTF-8 for worldwide language support", as mentioned above, worked in that case.

I've tried to explain this both in my initial question and as a response to those few who replies: the error output is not what always happens. I just included it for the cases where it does error out. When it does run the command, it *ignores the exclude rules*. That is, it dumps the data anyway. I thought I was crystal-clear when describing my problem, but no matter how careful I am, people always quote some specific part and focus on that, ignoring my overall explanation.

To be clear: The problem is not solved. I'm not one step closer to a solution. It's ignoring the rule or displaying the nonsensical errors, but never actually works.

I am afraid I must insist, pg_dump is expecting a shell that honors "client_encoding = 'UTF8'", and all the issues you are describing fit the mold of a CMD that is not doing so: fails when using extended characters with "invalid byte sequence for encoding "UTF8"" or gives wrong results, and works when you use plain ASCII.

Please read an excerpt from [1]:

"The current changes also don’t cover what is required for our “processed input mode” that presents an editable input line for applications like CMD.exe. We are planning and actively updating the code for popup windows, command aliases, command history, and the editable input line itself to support full true Unicode as well."

Not sure I can help any further if your system is below Windows 10 April 2018 Update (Version 1803) and cannot active true (but beta) UTF8 support. Maybe using a client from a POSIX machine as an alternative.


Regards,

Juan José Santamaría Flecha

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #16550: Problem with pg_service.conf
Next
From: Michał Lis
Date:
Subject: Re: BUG #16550: Problem with pg_service.conf