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-28 22:40:46
Message-ID: MDMYyn0--7-2@tutanota.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> come up with a minimal and self-contained reproducer, so that someone who does can try it and see what you see on your end.  So far you have only provided some terminal invocations accompanied by error messages and vague descriptions of comparing the actual and expected output of pg_dump.

Did you miss my e-mail starting with "After taking a longer break from my problem, I have now made a fresh, clean, scientifically conducted experiment in order to truly get to the bottom of this annoying problem once and for all."? (I don't now how I'd link to it.) There I go through everything with full commands and a minimal test database (which I also describe how I created).

I don't see how I could possibly create a smaller or clearer example of the issue. Whatever "strange things" cmd.exe does clearly doesn't show up for my cross-platform PHP CLI script. (I guess it's theoretically possible that PHP for Windows does some sort of "processing" automatically which pg_dump lacks, but I doubt it.)

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2020-07-28 23:31:43 Re: pg_dump seems to be broken in regards to the "--exclude-table-data" option on Windows.
Previous Message Tom Lane 2020-07-28 15:32:56 Re: BUG #16558: `AND FALSE` increases planning time of query on 2 tables with 1000 partitions to more than 7 seconds