From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | "Drouvot, Bertrand" <bertranddrouvot(dot)pg(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Record SET session in VariableSetStmt |
Date: | 2022-10-07 01:30:28 |
Message-ID: | Yz+BNO50qKKAKQmL@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 06, 2022 at 08:28:27PM +0800, Julien Rouhaud wrote:
> If we move to a real jumbling of VariableSetStmt, we should keep the rules
> consistent with the rest of the jumble code and ignore an explicit "SESSION" in
> the original command.
Hm, interesting bit, I should study more this area. So the query ID
calculation actually only cares about the contents of the Nodes
parsed, while the query string used is the one when the entry is
created for the first time. It seems like the patch to add
TransactionStmt nodes into the jumbling misses something here, as we'd
still compile different query IDs depending on the query string itself
for simple commands like BEGIN or COMMIT. I'll reply on the other
thread about all that..
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-10-07 02:06:47 | Re: use has_privs_of_role() for pg_hba.conf |
Previous Message | Michael Paquier | 2022-10-07 01:08:36 | Re: Issue with pg_stat_subscription_stats |