pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Process session_preload_libraries within InitPostgres's transact
Date: Mon, 25 Jul 2022 14:27:54 +0000
Message-ID: <E1oFz3p-001CKX-Bf@gemulon.postgresql.org> (raw)

Process session_preload_libraries within InitPostgres's transaction.

Previously we did this after InitPostgres, at a somewhat randomly chosen
place within PostgresMain.  However, since commit a0ffa885e doing this
outside a transaction can cause a crash, if we need to check permissions
while replacing a placeholder GUC.  (Besides which, a preloaded library
could itself want to do database access within _PG_init.)

To avoid needing an additional transaction start/end in every session,
move the process_session_preload_libraries call to within InitPostgres's
transaction.  That requires teaching the code not to call it when
InitPostgres is called from somewhere other than PostgresMain, since
we don't want session_preload_libraries to affect background workers.
The most future-proof solution here seems to be to add an additional
flag parameter to InitPostgres; fortunately, we're not yet very worried
about API stability for v15.

Doing this also exposed the fact that we're currently honoring
session_preload_libraries in walsenders, even those not connected to
any database.  This seems, at minimum, a POLA violation: walsenders
are not interactive sessions.  Let's stop doing that.

(All these comments also apply to local_preload_libraries, of course.)

Per report from Gurjeet Singh (thanks also to Nathan Bossart and Kyotaro
Horiguchi for review).  Backpatch to v15 where a0ffa885e came in.

Discussion: https://postgr.es/m/CABwTF4VEpwTHhRQ+q5MiC5ucngN-whN-PdcKeufX7eLSoAfbZA@mail.gmail.com

Branch
------
master

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

Modified Files
--------------
src/backend/bootstrap/bootstrap.c   |  2 +-
src/backend/postmaster/autovacuum.c |  7 +++---
src/backend/postmaster/postmaster.c | 12 +++++++--
src/backend/tcop/postgres.c         | 12 ++++-----
src/backend/utils/init/postinit.c   | 49 +++++++++++++++++++++++++++++--------
src/include/miscadmin.h             |  7 ++++--
6 files changed, 64 insertions(+), 25 deletions(-)



view thread (2+ messages)  latest in thread

Message-ID: <E1oFz3p-001CKX-Bf@gemulon.postgresql.org>
Permalink:  ../E1oFz3p-001CKX-Bf@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1oFz3p-001CKX-Bf@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-committers@postgresql.org
  Cc: tgl@sss.pgh.pa.us
  Subject: Re: pgsql: Process session_preload_libraries within InitPostgres's transact
  In-Reply-To: <E1oFz3p-001CKX-Bf@gemulon.postgresql.org>
  References: <E1oFz3p-001CKX-Bf@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox