| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
| Cc: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17288: PSQL bug with COPY command (Windows) |
| Date: | 2021-11-28 06:40:22 |
| Message-ID: | YaMkVha0ZwzHJk60@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Nov 28, 2021 at 01:15:36PM +0900, Michael Paquier wrote:
> Using directly psql commands in the tests is not a good idea as it
> makes the client-side execution more sensitive to the environment.
> src/test/perl/PostgreSQL/Test/Cluster.pm does the same work, in the
> wanted way, so it would be better to rely on it (see 384f1ab for one
> recent issue). A test with a minimal timeout also takes time, making
> for slower tests on faster machines.
Or, rather than relying on a small timeout, could we just send some
data to stdin and check the table's contents in return? That would
make the test faster, while not penalizing the coverage.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-11-28 16:51:06 | Re: BUG #17301: SELECT gets weird result while two transactions are submitted concurrently |
| Previous Message | Michael Paquier | 2021-11-28 04:15:36 | Re: BUG #17288: PSQL bug with COPY command (Windows) |