| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | "Imseih (AWS), Sami" <samimseih(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: query_id, pg_stat_activity, extended query protocol |
| Date: | 2024-09-03 14:49:31 |
| Message-ID: | 44901936-094d-431b-bb7c-328db0b7b03c@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 14/8/2024 23:05, Imseih (AWS), Sami wrote:
> There are no tests as this requires more discussion in a separate thread(?)
Unfortunately, TAP tests don't allow us to keep a connection and
manually permutate the order of queries sent to different connections.
But isolation tests are designed to do so. Of course, they aren't the
best if you need to compare values produced by various queries but see a
clumsy sketch doing that in the attachment.
Also, while writing the test, I found out that now, JumbleQuery takes
into account constants of the A_Const node, and calls of the same
prepared statement with different parameters generate different
query_id. Is it a reason to introduce JumbleQuery options and allow
different logic of queryid generation?
--
regards, Andrei Lepikhov
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-queryid-isolation-test.patch | text/plain | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2024-09-03 15:06:32 | Re: scalability bottlenecks with (many) partitions (and more) |
| Previous Message | Jim Jones | 2024-09-03 14:43:51 | Re: [PATCH] Add CANONICAL option to xmlserialize |