From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Race condition in recovery? |
Date: | 2021-06-12 14:20:24 |
Message-ID: | 2178605.1623507624@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I have pushed a fix, tested on a replica of fairywren/drongo,
This bit seems a bit random:
# WAL segment, this is enough to guarantee that the history file was
# archived.
my $archive_wait_query =
- "SELECT '$walfile_to_be_archived' <= last_archived_wal FROM pg_stat_archiver;";
+ "SELECT coalesce('$walfile_to_be_archived' <= last_archived_wal, false) " .
+ "FROM pg_stat_archiver";
$node_standby->poll_query_until('postgres', $archive_wait_query)
or die "Timed out while waiting for WAL segment to be archived";
my $last_archived_wal_file = $walfile_to_be_archived;
I wonder whether that is a workaround for the poll_query_until bug
I proposed to fix at [1].
regards, tom lane
[1] https://www.postgresql.org/message-id/2130215.1623450521%40sss.pgh.pa.us
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-06-12 14:35:08 | Re: Use pg_nextpower2_* in a few more places |
Previous Message | Zhihong Yu | 2021-06-12 14:13:09 | Re: Use pg_nextpower2_* in a few more places |