Re: pg_dump seems to be broken in regards to the "--exclude-table-data" option on Windows.

From: tutiluren(at)tutanota(dot)com
To: Pgsql Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump seems to be broken in regards to the "--exclude-table-data" option on Windows.
Date: 2020-07-26 22:28:00
Message-ID: MDCELjU--3-2@tutanota.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Since at least part of your struggle has been with cmd.exe not handling UTF8 well, I wonder if you have considered Windows Terminal, which purports to handle UTF8 better?
>
> https://www.microsoft.com/en-us/p/windows-terminal/9n0dx20hk701
>
> I'm not saying it will solve everything, but it might at least remove one layer of confusion.
>

Well, I'll probably start using that "Windows Terminal" thing when it actually is built into Windows. I've heard it mentioned numerous times, but it's some kind of "external download" and involves the vile "Windows Store" on top of it, and I know it will cause numerous issues since everything about my system expects cmd.exe. I spent ages trying to get PowerShell (which is apparently now already outdated if Windows Terminal is the new "hot" terminal to use...) to work properly, but it never did, and thus I'm not very eager to switch.

Plus nothing else other than pg_dump has any problems with Unicode, so that's also a bit... odd.

PS: I actually just tried following the link to download it, but it just gets stuck at a nag screen to make me "log in" to my (nonexistent) "Microsoft account". Ugh. Not a chance. Sorry.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message tutiluren 2020-07-26 23:06:12 Re: pg_dump seems to be broken in regards to the "--exclude-table-data" option on Windows.
Previous Message Tom Lane 2020-07-26 21:57:33 Re: BUG #16555: Postgresql is not LTO ready