From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: psql: Add test for query canceling |
Date: | 2021-08-25 05:37:22 |
Message-ID: | alpine.DEB.2.22.394.2108250705270.2232211@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
> That looks pretty solid to me, and I can confirm that it passes
> on wrasse's host. The only nit I can find to pick is that this:
>
> + usleep(10_000) until -s "$tempdir/psql.pid" or ($count++ > 180 * 100 and die 'pid file did not appear');
>
> basically assumes that psql.pid will be written atomically.
> It'd be marginally safer to wait till psql.pid can be seen to
> contain a newline. I don't think that would be too hard to do,
> if you put the slurp_file call inside the wait loop and inspect
> its result.
I finally came around to have a look at the patch.
For the issue raised above, I can see that the file could be created but
not yet written, but as the patch waits for the file to be non zero, ISTM
that the probability of a torn write of a single integer by echo is so
remote that we could let it as that?
Attached a version with the slurping in the loop anyway.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
0001-Make-psql-cancel-test-more-timing-robust-2.patch | text/x-diff | 2.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-08-25 06:17:39 | pgsql: Fix incorrect merge in ECPG code with DECLARE |
Previous Message | Amit Kapila | 2021-08-25 04:49:58 | pgsql: Fix toast rewrites in logical decoding. |