From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Atul Kumar <akumar14871(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: log_statement vs log_min_duration_statement |
Date: | 2023-09-26 23:51:31 |
Message-ID: | CAMkU=1xX6Gq_zBr3fjsceqqgKKf0UPLci4SKaqsUd=OFsddWNA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 26, 2023 at 5:33 PM Atul Kumar <akumar14871(at)gmail(dot)com> wrote:
> Hi,
>
> I have a query about parameters and log_statement
>
> my postgres version is 12 and running on centos 7
>
> my log_statement is set to "DDL".
>
> and log_min_duration_statement is set to "1ms"
>
> so technically it should log "ONLY DDLs" that take more than 1ms.
>
> but to my surprise, postgres is logging DML as well which is taking more
> than 1ms.
>
That doesn't surprise me, it is just what I expected.
>
> What am I missing here to understand, because as per my understanding
> log_statement and log_min_duration_statement are correlated, postgres
> should log according to log_statement parameter.
>
If something in the docs led you to this misunderstanding, we should
identify it and fix it. Otherwise, there isn't much we can do, except
point out that that is simply not how it works.
Cheers,
Jeff
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-09-27 00:25:36 | Re: Ad hoc SETOF type definition? |
Previous Message | Erik Wienhold | 2023-09-26 21:47:49 | Re: Early binding of CURRENT_SCHEMA (Was: CREATE FUNCTION ... SEARCH {, DEFAULT | SYSTEM | SESSION }) |