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)
