pgsql: Add tab completion for data types after ALTER TABLE ADD [COLUMN]

2021-08-30 Thread Michael Paquier
Add tab completion for data types after ALTER TABLE ADD [COLUMN] in psql This allows finding data types that can be used for the creation of a new column, completing d3fa876. Author: Dagfinn Ilmari Mannsåker Discussion: https://postgr.es/m/87h7f7uk6s@wibble.ilmari.org Branch -- master D

pgsql: Refactor one use of IDENTIFY_SYSTEM in WAL streaming code of pg_

2021-08-30 Thread Michael Paquier
Refactor one use of IDENTIFY_SYSTEM in WAL streaming code of pg_basebackup 0c013e0 has done a large refactoring to unify all the code paths using replication commands, but forgot one code path doing WAL streaming that checks the validity of a cluster connecting to with IDENTIFY_SYSTEM. There is a

pgsql: Report tuple address in data-corruption error message

2021-08-30 Thread Alvaro Herrera
Report tuple address in data-corruption error message Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and la

pgsql: Report tuple address in data-corruption error message

2021-08-30 Thread Alvaro Herrera
Report tuple address in data-corruption error message Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and la

pgsql: Report tuple address in data-corruption error message

2021-08-30 Thread Alvaro Herrera
Report tuple address in data-corruption error message Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and la

pgsql: Report tuple address in data-corruption error message

2021-08-30 Thread Alvaro Herrera
Report tuple address in data-corruption error message Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and la

pgsql: Report tuple address in data-corruption error message

2021-08-30 Thread Alvaro Herrera
Report tuple address in data-corruption error message Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and la

pgsql: Report tuple address in data-corruption error message

2021-08-30 Thread Alvaro Herrera
Report tuple address in data-corruption error message Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and la

pgsql: Report tuple address in data-corruption error message

2021-08-30 Thread Alvaro Herrera
Report tuple address in data-corruption error message Most data-corruption reports mention the location of the problem, but this one failed to. Add it. Backpatch all the way back. In 12 and older, also assign the ERRCODE_DATA_CORRUPTED error code as was done in commit fd6ec93bf890 for 13 and la

pgsql: psql: Fix name quoting on extended statistics

2021-08-30 Thread Alvaro Herrera
psql: Fix name quoting on extended statistics Per our message style guidelines, for human consumption we quote qualified names as a whole rather than each part separately; but commits bc085205c8a4 introduced a deviation for extended statistics and a4d75c86bf15 copied it. I don't agree with this p

pgsql: psql: Fix name quoting on extended statistics

2021-08-30 Thread Alvaro Herrera
psql: Fix name quoting on extended statistics Per our message style guidelines, for human consumption we quote qualified names as a whole rather than each part separately; but commits bc085205c8a4 introduced a deviation for extended statistics and a4d75c86bf15 copied it. I don't agree with this p

pgsql: pgbench: Avoid unnecessary measurement of connection delays.

2021-08-30 Thread Fujii Masao
pgbench: Avoid unnecessary measurement of connection delays. Commit 547f04e734 changed pgbench so that it used the measurement result of connection delays in its benchmark report only when -C/--connect option is specified. But previously those delays were unnecessarily measured even when that opti

pgsql: pgbench: Avoid unnecessary measurement of connection delays.

2021-08-30 Thread Fujii Masao
pgbench: Avoid unnecessary measurement of connection delays. Commit 547f04e734 changed pgbench so that it used the measurement result of connection delays in its benchmark report only when -C/--connect option is specified. But previously those delays were unnecessarily measured even when that opti

Re: pgsql: psql: Add test for query canceling

2021-08-30 Thread Daniel Gustafsson
> On 30 Aug 2021, at 06:27, Michael Paquier wrote: > > On Thu, Aug 26, 2021 at 08:39:31AM +0200, Peter Eisentraut wrote: >> It looks like this fixed it. Thanks all. > > conchuela has complained today on this test, as of HEAD: > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=conchuela&d

pgsql: Add list of acknowledgments to release notes

2021-08-30 Thread Peter Eisentraut
Add list of acknowledgments to release notes This contains all individuals mentioned in the commit messages during PostgreSQL 14 development. current through ed740b06b18e1a23becd54c97ff229aba4c94349 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/7af5c38eb9d