Re: pgsql: Respect permissions within logical replication.

2022-01-08 Thread Michael Paquier
On Sat, Jan 08, 2022 at 02:22:23PM +0900, Michael Paquier wrote: > 2) crake fails perl-check > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2022-01-08%2002%3A47%3A26 > > All the failures are the same, because of the shape of the subroutine > definitions: > Jan 07 21:53:04 ./src

Re: pgsql: Respect permissions within logical replication.

2022-01-08 Thread Andrew Dunstan
On 1/8/22 04:25, Michael Paquier wrote: > On Sat, Jan 08, 2022 at 02:22:23PM +0900, Michael Paquier wrote: >> 2) crake fails perl-check >> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2022-01-08%2002%3A47%3A26 >> >> All the failures are the same, because of the shape of the su

pgsql: Fix pgperlcritic complaint, per buildfarm.

2022-01-08 Thread Jeff Davis
Fix pgperlcritic complaint, per buildfarm. Author: Michael Paquier Discussion: https://postgr.es/m/YdlYfS/l%2BPQA0ehs%40paquier.xyz Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f1e90859cef3f48f45578390acf63c6f7fd61697 Modified Files -- src/test/subsc

pgsql: Fix results of index-only scans on btree_gist char(N) indexes.

2022-01-08 Thread Tom Lane
Fix results of index-only scans on btree_gist char(N) indexes. If contrib/btree_gist is used to make a GIST index on a char(N) (bpchar) column, and that column is retrieved via an index-only scan, what came out had all trailing spaces removed. Since that doesn't happen in any other kind of table

pgsql: Fix results of index-only scans on btree_gist char(N) indexes.

2022-01-08 Thread Tom Lane
Fix results of index-only scans on btree_gist char(N) indexes. If contrib/btree_gist is used to make a GIST index on a char(N) (bpchar) column, and that column is retrieved via an index-only scan, what came out had all trailing spaces removed. Since that doesn't happen in any other kind of table

pgsql: Fix results of index-only scans on btree_gist char(N) indexes.

2022-01-08 Thread Tom Lane
Fix results of index-only scans on btree_gist char(N) indexes. If contrib/btree_gist is used to make a GIST index on a char(N) (bpchar) column, and that column is retrieved via an index-only scan, what came out had all trailing spaces removed. Since that doesn't happen in any other kind of table

pgsql: Fix results of index-only scans on btree_gist char(N) indexes.

2022-01-08 Thread Tom Lane
Fix results of index-only scans on btree_gist char(N) indexes. If contrib/btree_gist is used to make a GIST index on a char(N) (bpchar) column, and that column is retrieved via an index-only scan, what came out had all trailing spaces removed. Since that doesn't happen in any other kind of table

pgsql: Fix results of index-only scans on btree_gist char(N) indexes.

2022-01-08 Thread Tom Lane
Fix results of index-only scans on btree_gist char(N) indexes. If contrib/btree_gist is used to make a GIST index on a char(N) (bpchar) column, and that column is retrieved via an index-only scan, what came out had all trailing spaces removed. Since that doesn't happen in any other kind of table

pgsql: Fix results of index-only scans on btree_gist char(N) indexes.

2022-01-08 Thread Tom Lane
Fix results of index-only scans on btree_gist char(N) indexes. If contrib/btree_gist is used to make a GIST index on a char(N) (bpchar) column, and that column is retrieved via an index-only scan, what came out had all trailing spaces removed. Since that doesn't happen in any other kind of table

pgsql: More cleanup of a2ab9c06ea.

2022-01-08 Thread Jeff Davis
More cleanup of a2ab9c06ea. Require SELECT privileges when performing UPDATE or DELETE, to be consistent with the way a normal UPDATE or DELETE command works. Simplify subscription test it so that it runs faster. Also, wait for initial table sync to complete to avoid intermittent failures. Minor