Re: Query Jumbling for CALL and SET utility statements - Mailing list pgsql-hackers

From Imseih (AWS), Sami
Subject Re: Query Jumbling for CALL and SET utility statements
Date
Msg-id 4E9B4BE0-1ADA-4828-9AE7-9A2A4002F9DE@amazon.com
Whole thread Raw
In response to Re: Query Jumbling for CALL and SET utility statements  ("Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>)
Responses Re: Query Jumbling for CALL and SET utility statements  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
> I've been thinking since the beginning of this thread that there
> was no coherent, defensible rationale being offered for jumbling
> some utility statements and not others.

+1 to the idea, as there are other utility statement cases
that should be Jumbled. Here is a recent thread for jumbling
cursors [1].

The CF entry [2] has been withdrawn until consensus is reached
on this topic.

[1]: https://www.postgresql.org/message-id/203CFCF7-176E-4AFC-A48E-B2CECFECD6AA@amazon.com
[2]: https://commitfest.postgresql.org/40/3901/


Regards,

Sami Imseih
AWS (Amazon Web Services)





pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: subtransaction performance
Next
From: Dmitry Koval
Date:
Subject: Re: Frontend error logging style