| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Jon Erdman <jon(at)thewickedtribe(dot)net> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Good News Everyone! + feature proposal |
| Date: | 2023-10-05 16:02:15 |
| Message-ID: | CAOBaU_Y=vOaDkS_PBMuhT=xUOJOufb_xfh-Nv+E_VjQsSKg26Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 5, 2023 at 11:11 PM Jon Erdman <jon(at)thewickedtribe(dot)net> wrote:
>
> As a second more general question: could my original idea (i.e. sans
> event trigger) be implemented in an extension somehow, or is that not
> technically possible (I suspect not)?
It should be easy to do using the ProcessUtility_hook hook, defined in
a custom module written in C. As long as your module is preloaded
(one of the *_preload_libraries GUC), your code will be called without
the need for any SQL-level object and you would be free to add any
custom GUC you want to enable it on a per-user basis or anything else.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Drouvot, Bertrand | 2023-10-05 16:02:43 | Re: Add a new BGWORKER_BYPASS_ROLELOGINCHECK flag |
| Previous Message | Peter Eisentraut | 2023-10-05 15:49:24 | Re: tablecmds.c/MergeAttributes() cleanup |