| From: | Étienne BERSAC <etienne(dot)bersac(at)dalibo(dot)com> |
|---|---|
| To: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, jtc331(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: RFC: Logging plan of the running query |
| Date: | 2023-10-27 12:54:48 |
| Message-ID: | 6d13f7485091f51ad7d11cb7c65f75038c10d747.camel@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg스포츠 토토SQL |
> Hi,
>
> If we use client log message, that message is shown on the target
> process whose pid is specified by the parameter of
> pg_log_query_plan():
>
> (pid:1000)=# select pg_sleep(60);
> (pid:1001)=# select pg_log_query_plan(1000);
> (pid:1000)=# LOG: query plan running on backend with PID 1000 is:
> Query Text: select pg_sleep(1000);
> Result (cost=0.00..0.01 rows=1 width=4)
> Output: pg_sleep('1000'::double precision)
>
> I think this is not an expected behavior and we set elevel to
> LOG_SERVER_ONLY.
Makes sens. Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2023-10-27 12:56:14 | Re: btree_gin: Incorrect leftmost interval value |
| Previous Message | Heikki Linnakangas | 2023-10-27 12:42:52 | Re: btree_gin: Incorrect leftmost interval value |