| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Subject: | Re: Set query_id for query contained in utility statement |
| Date: | 2024-11-16 20:43:12 |
| Message-ID: | 202411162043.lhyqsgw72kxe@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-Oct-24, Michael Paquier wrote:
> Track more precisely query locations for nested statements
I just noticed that this commit broke pgaudit pretty thoroughly. I'm
not sure if this means pgaudit needs changes, or this commit needs to be
reconsidered in some way; at this point I'm just raising the alarm.
(FWIW there are a few other pgaudit-breaking changes in 18, but they
don't seem as bad as this one, to the extent that the fixes likely
belong into pgaudit.)
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"I apologize for the confusion in my previous responses.
There appears to be an error." (ChatGPT)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2024-11-16 20:44:04 | Re: CI and test improvements |
| Previous Message | Andres Freund | 2024-11-16 20:22:57 | Re: CI and test improvements |