Re: pgsql: Fix handling of WAL segments ready to be archived during crash r

2020-04-27 Thread Jehan-Guillaume de Rorthais
On Sat, 25 Apr 2020 09:31:14 +0900 Michael Paquier wrote: > On Fri, Apr 24, 2020 at 05:30:21PM +0900, Kyotaro Horiguchi wrote: > > I think we can reimplement them by waiting > > pg_stat_archiver.last_failed_wal at least for archive_mode=always > > case. I'm not sure about the case where archive_m

pgsql: pg_dump: Replace can't-happen error with assertion

2020-04-27 Thread Peter Eisentraut
pg_dump: Replace can't-happen error with assertion Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/d51f704fd8cbae03cd9b29fe103dd027d521ff04 Modified Files -- src/bin/pg_dump/pg_backup_tar.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

pgsql: Doc: render π more nicely in PDF output.

2020-04-27 Thread Tom Lane
Doc: render π more nicely in PDF output. We need to select symbol font explicitly, or it comes out misaligned. Alexander Lakhin, Tom Lane Discussion: https://postgr.es/m/[email protected] Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/5ac24755485a5c1

pgsql: Fix full text search to handle NOT above a phrase search correct

2020-04-27 Thread Tom Lane
Fix full text search to handle NOT above a phrase search correctly. Queries such as '!(foo<->bar)' failed to find matching rows when implemented as a GiST or GIN index search. That's because of failing to handle phrase searches as tri-valued when considering a query without any position informati

pgsql: Fix full text search to handle NOT above a phrase search correct

2020-04-27 Thread Tom Lane
Fix full text search to handle NOT above a phrase search correctly. Queries such as '!(foo<->bar)' failed to find matching rows when implemented as a GiST or GIN index search. That's because of failing to handle phrase searches as tri-valued when considering a query without any position informati

pgsql: Fix full text search to handle NOT above a phrase search correct

2020-04-27 Thread Tom Lane
Fix full text search to handle NOT above a phrase search correctly. Queries such as '!(foo<->bar)' failed to find matching rows when implemented as a GiST or GIN index search. That's because of failing to handle phrase searches as tri-valued when considering a query without any position informati

pgsql: Fix full text search to handle NOT above a phrase search correct

2020-04-27 Thread Tom Lane
Fix full text search to handle NOT above a phrase search correctly. Queries such as '!(foo<->bar)' failed to find matching rows when implemented as a GiST or GIN index search. That's because of failing to handle phrase searches as tri-valued when considering a query without any position informati

pgsql: Fix full text search to handle NOT above a phrase search correct

2020-04-27 Thread Tom Lane
Fix full text search to handle NOT above a phrase search correctly. Queries such as '!(foo<->bar)' failed to find matching rows when implemented as a GiST or GIN index search. That's because of failing to handle phrase searches as tri-valued when considering a query without any position informati

pgsql: Fix bogus tar-file padding logic for standby.signal.

2020-04-27 Thread Robert Haas
Fix bogus tar-file padding logic for standby.signal. When pg_basebackup -R is used, we inject standby.signal into the tar file for the main tablespace. The proper thing to do is to pad each file injected into the tar file out to a 512-byte boundary by appending nulls, but here the file is of lengt

pgsql: Fix bogus tar-file padding logic for standby.signal.

2020-04-27 Thread Robert Haas
Fix bogus tar-file padding logic for standby.signal. When pg_basebackup -R is used, we inject standby.signal into the tar file for the main tablespace. The proper thing to do is to pad each file injected into the tar file out to a 512-byte boundary by appending nulls, but here the file is of lengt

pgsql: Add more TAP coverage for archive status with crash recovery of

2020-04-27 Thread Michael Paquier
Add more TAP coverage for archive status with crash recovery of standbys This part of the test was included originally in 4e87c48, but got reverted as of f9c1b8d because of timing issues in the test, where, after more analysis, we found that the standbys may not have recovered from the archives al