From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, michael(at)paquier(dot)xyz, gurjeet(at)singh(dot)im, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Unprivileged user can induce crash by using an SUSET param in PGOPTIONS |
Date: | 2022-07-23 17:23:24 |
Message-ID: | 954936.1658597004@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Nathan Bossart <nathandbossart(at)gmail(dot)com> writes:
> On Fri, Jul 22, 2022 at 06:44:04PM -0400, Tom Lane wrote:
>> Another idea is to add a "bool interactive" parameter to InitPostgres,
>> thereby shoving the issue out to the call sites. Still wouldn't
>> expose the am_walsender angle, but conceivably it'd be more
>> future-proof anyway?
> I hesitated to suggest this exactly because of the WAL sender problem, but
> it does seem slightly more future-proof, so +1 for this approach.
So about like this then. (I spent some effort on cleaning up the
disjointed-to-nonexistent presentation of InitPostgres' parameters.)
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
move-process_session_preload_libraries-3.patch | text/x-diff | 8.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2022-07-23 17:27:56 | Re: Handle infinite recursion in logical replication setup |
Previous Message | Zheng Li | 2022-07-23 16:23:51 | Re: Support logical replication of DDLs |