pgsql: Fix possible logical replication crash.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix possible logical replication crash.
Date: 2023-04-03 17:54:37
Message-ID: E1pjOO4-001C49-JE@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Fix possible logical replication crash.

Commit c3afe8cf5a1e465bd71e48e4bc717f5bfdc7a7d6 added a new
password_required option but forgot that you need database access
to check whether an arbitrary role ID is a superuser.

Report and patch by Hou Zhijie. I added a comment. Thanks to
Alexander Lakhin for devising a way to reproduce the crash.

Discussion: http://postgr.es/m/OS0PR01MB5716BFD7EC44284C89F40808948F9@OS0PR01MB5716.jpnprd01.prod.outlook.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/e7e7da2f8d57bbe6c8fb463a9eec51486000ba2e

Modified Files
--------------
src/backend/replication/logical/worker.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2023-04-03 18:02:07 pgsql: Move heaprel struct field next to index rel field.
Previous Message Tom Lane 2023-04-03 14:18:41 pgsql: When using valgrind, log the current query after an error is det