| From: | Ignat Remizov <ignat980(at)gmail(dot)com> |
|---|---|
| To: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM |
| Date: | 2025-12-03 19:38:57 |
| Message-ID: | CAKiC8XYAN6ciOZnErMzwZeeFW+Ud4b-e1_aBO9bwa6iRkFveZw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Kirill,
These are great examples, thanks. I wasn't aware it was that easy to chain
config overwrite and crash/restart from plain SQL.
Taken together, that makes it clear this GUC buys less than I'd hoped, and
is probably not worth the extra complexity on its own.
Please consider this patch withdrawn for now. I'll go back and think about
a more comprehensive approach (e.g. a single control over superuser
features), and if something useful comes out of that I'll post a separate
proposal. I'll also play with the panic cases you mentioned as part of that.
Thanks again for the detailed explanations.
--
Ignat Remizov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-12-03 20:07:56 | Re: Proposal: Add a callback data parameter to GetNamedDSMSegment |
| Previous Message | Jacob Champion | 2025-12-03 19:35:07 | Re: [PATCH] Add enable_copy_program GUC to control COPY PROGRAM |