[COMMITTERS] pgsql: Document how logical replication deals with statement triggers

Document how logical replication deals with statement triggers Reported-by: Константин Евтеев Bug: #14699 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/012d83f57aff973a73214262f3d87105786e3500 Modified Files -- doc/src/sgml/logical-replication.sgml |

[COMMITTERS] pgsql: Improve subscription locking

Improve subscription locking This avoids "tuple concurrently updated" errors when a ALTER or DROP SUBSCRIPTION writes to pg_subscription_rel at the same time as a worker. Author: Petr Jelinek Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/cb9079cd51a2df677dc182ae

[COMMITTERS] pgsql: Don't mention SSL methods that aren't reachable in docs

Don't mention SSL methods that aren't reachable in docs Author: Michael Paquier Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/42794d6749f24636efbb198db17c30c63df10900 Modified Files -- doc/src/sgml/libpq.sgml | 3 +-- doc/src/sgml/sslinfo.sgml | 4 +

[COMMITTERS] pgsql: Treat clean shutdown of an SSL connection same as the non-SSL ca

Treat clean shutdown of an SSL connection same as the non-SSL case. If the client closes an SSL connection, treat it the same as EOF on a non-SSL connection. In particular, don't write a message in the log about that. Michael Paquier. Discussion: https://www.postgresql.org/message-id/cab7npqsfy

[COMMITTERS] pgsql: Treat clean shutdown of an SSL connection same as the non-SSL ca

Treat clean shutdown of an SSL connection same as the non-SSL case. If the client closes an SSL connection, treat it the same as EOF on a non-SSL connection. In particular, don't write a message in the log about that. Michael Paquier. Discussion: https://www.postgresql.org/message-id/cab7npqsfy

[COMMITTERS] pgsql: Treat clean shutdown of an SSL connection same as the non-SSL ca

Treat clean shutdown of an SSL connection same as the non-SSL case. If the client closes an SSL connection, treat it the same as EOF on a non-SSL connection. In particular, don't write a message in the log about that. Michael Paquier. Discussion: https://www.postgresql.org/message-id/cab7npqsfy

[COMMITTERS] pgsql: Treat clean shutdown of an SSL connection same as the non-SSL ca

Treat clean shutdown of an SSL connection same as the non-SSL case. If the client closes an SSL connection, treat it the same as EOF on a non-SSL connection. In particular, don't write a message in the log about that. Michael Paquier. Discussion: https://www.postgresql.org/message-id/cab7npqsfy

[COMMITTERS] pgsql: Treat clean shutdown of an SSL connection same as the non-SSL ca

Treat clean shutdown of an SSL connection same as the non-SSL case. If the client closes an SSL connection, treat it the same as EOF on a non-SSL connection. In particular, don't write a message in the log about that. Michael Paquier. Discussion: https://www.postgresql.org/message-id/cab7npqsfy

[COMMITTERS] pgsql: Treat clean shutdown of an SSL connection same as the non-SSL ca

Treat clean shutdown of an SSL connection same as the non-SSL case. If the client closes an SSL connection, treat it the same as EOF on a non-SSL connection. In particular, don't write a message in the log about that. Michael Paquier. Discussion: https://www.postgresql.org/message-id/cab7npqsfy

[COMMITTERS] pgsql: Forbid gen_random_uuid() with --disable-strong-random

Forbid gen_random_uuid() with --disable-strong-random Previously, gen_random_uuid() would fall back to a weak random number generator, unlike gen_random_bytes() which would just fail. And this was not made very clear in the docs. For consistency, also make gen_random_uuid() fail outright, if compi