pgsql: Fix incorrect format placeholder

2024-05-07 Thread Peter Eisentraut
Fix incorrect format placeholder Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6d716adf8569b734eb8849094e9b3edab084c7f8 Modified Files -- src/backend/replication/logical/slotsync.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: Ensure that "pg_restore -l" reports dependent TOC entries correc

2024-05-07 Thread Tom Lane
Ensure that "pg_restore -l" reports dependent TOC entries correctly. If -l was specified together with selective-restore options such as -n or -N, dependent TOC entries such as comments would be omitted from the listing, even when an actual restore would have selected them. This happened because P

pgsql: Ensure that "pg_restore -l" reports dependent TOC entries correc

2024-05-07 Thread Tom Lane
Ensure that "pg_restore -l" reports dependent TOC entries correctly. If -l was specified together with selective-restore options such as -n or -N, dependent TOC entries such as comments would be omitted from the listing, even when an actual restore would have selected them. This happened because P

pgsql: Ensure that "pg_restore -l" reports dependent TOC entries correc

2024-05-07 Thread Tom Lane
Ensure that "pg_restore -l" reports dependent TOC entries correctly. If -l was specified together with selective-restore options such as -n or -N, dependent TOC entries such as comments would be omitted from the listing, even when an actual restore would have selected them. This happened because P

pgsql: Ensure that "pg_restore -l" reports dependent TOC entries correc

2024-05-07 Thread Tom Lane
Ensure that "pg_restore -l" reports dependent TOC entries correctly. If -l was specified together with selective-restore options such as -n or -N, dependent TOC entries such as comments would be omitted from the listing, even when an actual restore would have selected them. This happened because P

pgsql: Ensure that "pg_restore -l" reports dependent TOC entries correc

2024-05-07 Thread Tom Lane
Ensure that "pg_restore -l" reports dependent TOC entries correctly. If -l was specified together with selective-restore options such as -n or -N, dependent TOC entries such as comments would be omitted from the listing, even when an actual restore would have selected them. This happened because P

pgsql: Ensure that "pg_restore -l" reports dependent TOC entries correc

2024-05-07 Thread Tom Lane
Ensure that "pg_restore -l" reports dependent TOC entries correctly. If -l was specified together with selective-restore options such as -n or -N, dependent TOC entries such as comments would be omitted from the listing, even when an actual restore would have selected them. This happened because P

pgsql: Don't corrupt plpython's "TD" dictionary in a recursive trigger

2024-05-07 Thread Tom Lane
Don't corrupt plpython's "TD" dictionary in a recursive trigger call. If a plpython-language trigger caused another one to be invoked, the "TD" dictionary created for the inner one would overwrite the outer one's "TD" dictionary. This is more or less the same problem that 1d2fe56e4 fixed for ordi

pgsql: Don't corrupt plpython's "TD" dictionary in a recursive trigger

2024-05-07 Thread Tom Lane
Don't corrupt plpython's "TD" dictionary in a recursive trigger call. If a plpython-language trigger caused another one to be invoked, the "TD" dictionary created for the inner one would overwrite the outer one's "TD" dictionary. This is more or less the same problem that 1d2fe56e4 fixed for ordi

pgsql: Don't corrupt plpython's "TD" dictionary in a recursive trigger

2024-05-07 Thread Tom Lane
Don't corrupt plpython's "TD" dictionary in a recursive trigger call. If a plpython-language trigger caused another one to be invoked, the "TD" dictionary created for the inner one would overwrite the outer one's "TD" dictionary. This is more or less the same problem that 1d2fe56e4 fixed for ordi

pgsql: Don't corrupt plpython's "TD" dictionary in a recursive trigger

2024-05-07 Thread Tom Lane
Don't corrupt plpython's "TD" dictionary in a recursive trigger call. If a plpython-language trigger caused another one to be invoked, the "TD" dictionary created for the inner one would overwrite the outer one's "TD" dictionary. This is more or less the same problem that 1d2fe56e4 fixed for ordi

pgsql: Don't corrupt plpython's "TD" dictionary in a recursive trigger

2024-05-07 Thread Tom Lane
Don't corrupt plpython's "TD" dictionary in a recursive trigger call. If a plpython-language trigger caused another one to be invoked, the "TD" dictionary created for the inner one would overwrite the outer one's "TD" dictionary. This is more or less the same problem that 1d2fe56e4 fixed for ordi

pgsql: Don't corrupt plpython's "TD" dictionary in a recursive trigger

2024-05-07 Thread Tom Lane
Don't corrupt plpython's "TD" dictionary in a recursive trigger call. If a plpython-language trigger caused another one to be invoked, the "TD" dictionary created for the inner one would overwrite the outer one's "TD" dictionary. This is more or less the same problem that 1d2fe56e4 fixed for ordi

pgsql: Fix assorted bugs related to identity column in partitioned tabl

2024-05-07 Thread Peter Eisentraut
Fix assorted bugs related to identity column in partitioned tables When changing the data type of a column of a partitioned table, craft the ALTER SEQUENCE command only once. Partitions do not have identity sequences of their own and thus do not need a ALTER SEQUENCE command for each partition.

Re: pgsql: Support C.UTF-8 locale in the new builtin collation provider.

2024-05-07 Thread Jeff Davis
On Thu, 2024-05-02 at 09:34 +0200, Peter Eisentraut wrote: > This commit changed the functions builtin_locale_encoding() and > builtin_validate_locale() in pg_locale.c, but did not update the > comments that claim that "C" is the only supported locale name. > > (I think it would be best to remov

pgsql: Remove obsolete comment.

2024-05-07 Thread Jeff Davis
Remove obsolete comment. Per suggestion from Peter, the comment was not helpful, so remove it rather than fixing it. Reported-by: Peter Eisentraut Discussion: https://postgr.es/m/d9421b21-e759-4b74-a039-c487b469c...@eisentraut.org Branch -- master Details --- https://git.postgresql.org

pgsql: Prevent RLS filters on ctid from breaking WHERE CURRENT OF

2024-05-07 Thread Tom Lane
Prevent RLS filters on ctid from breaking WHERE CURRENT OF . The executor only supports CurrentOfExpr as the sole tidqual of a TidScan plan node. tidpath.c failed to take any particular care about that, but would just take the first ctid equality qual it could find in the target relation's basere

pgsql: doc: Improve order of options on pgbench reference page

2024-05-07 Thread Peter Eisentraut
doc: Improve order of options on pgbench reference page Both the pgbench --help output and the reference page have sections for initialization options, benchmarking options, and common options. But the --debug option ended up in the wrong place on the reference page. Fix that by making the docume