From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Further stabilize results of 019_replslot_limit.pl. |
Date: | 2020-04-09 21:29:04 |
Message-ID: | [email protected] |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Further stabilize results of 019_replslot_limit.pl.
Depending on specific values of restart_lsn or pg_current_wal_lsn()
is obviously unsafe. The previous coding tried to dodge this issue
by rounding off, but that's not good enough, as shown by multiple
buildfarm members. Nuke all the uses of these values except for
null-ness checks, pending some credible argument why we should think
something else could be usefully stable.
Kyotaro Horiguchi, further modified by me
Discussion: https://postgr.es/m/[email protected]
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/e083fa34ced0d53807a57482048bb4c135c3d006
Modified Files
--------------
src/test/recovery/t/019_replslot_limit.pl | 34 +++++++++++++++----------------
1 file changed, 17 insertions(+), 17 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-04-09 21:31:59 | Re: pgsql: Remove testing for precise LSN/reserved bytes in new TAP test |
Previous Message | Tom Lane | 2020-04-09 19:39:28 | pgsql: Further cleanup of ts_headline code. |