From: | Amit Kapila <akapila(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Fix possible crash in tablesync worker. |
Date: | 2023-06-15 03:12:05 |
Message-ID: | E1q9dP2-001rOJ-U6@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix possible crash in tablesync worker.
Commit c3afe8cf5a added a new password_required option but forgot that you
need database access to check whether an arbitrary role ID is a superuser.
Commit e7e7da2f8d fixed a similar bug in apply worker, and this patch
fixes a similar bug in tablesync worker.
Author: Hou Zhijie
Reviewed-by: Amit Kapila
Discussion: https://postgr.es/m/OS0PR01MB571607F5A9D723755268D36294759@OS0PR01MB5716.jpnprd01.prod.outlook.com
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/b5c517379a40fa1af84c0852aa3730a5875a6482
Modified Files
--------------
src/backend/replication/logical/tablesync.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-06-15 04:46:18 | pgsql: intarray: Prevent out-of-bound memory reads with gist__int_ops |
Previous Message | Noah Misch | 2023-06-14 12:35:40 | pgsql: Make parseNodeString() C idiom compatible with Visual Studio 201 |