Re: RFC: Logging plan of the running query

From: Ekaterina Sokolova <e(dot)sokolova(at)postgrespro(dot)ru>
To: torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: RFC: Logging plan of the running query
Date: 2021-11-17 13:44:51
Message-ID: d5b390ba34e9914a3f73a8be936000a8@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

You forgot my last fix to build correctly on Mac. I have added it.

About our discussion of pg_query_state:

torikoshia писал 2021-11-04 15:49:
>> I doubt that it was the right link.
> Sorry for make you confused, here is the link.
> https://www.postgresql.org/message-id/CA%2BTgmobkpFV0UB67kzXuD36--OFHwz1bs%3DL_6PZbD4nxKqUQMw%40mail.gmail.com

Thank you. I'll see it soon.

> I imagined the following procedure.
> Does it cause dead lock in pg_query_state?
>
> - session1
> BEGIN; TRUNCATE t;
>
> - session2
> BEGIN; TRUNCATE t; -- wait
>
> - session1
> SELECT * FROM pg_query_state(<pid of session>); -- wait and dead
> locked?

As I know, pg_query_state use non-blocking read and write. I have wrote
few tests trying to deadlock it (on 14 version), but all finished
correctly.

Have a nice day. Please feel free to contact me if you need any further
information.

--
Ekaterina Sokolova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Attachment Content-Type Size
v13-0002-log-running-query-plan.patch text/x-diff 28.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-11-17 13:49:21 Re: Propose a new hook for mutating the query bounds
Previous Message Daniel Gustafsson 2021-11-17 13:43:06 Re: Logical Replication - improve error message while adding tables to the publication in check_publication_add_relation