Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements

From: Seino Yuki <seinoyu(at)oss(dot)nttdata(dot)com>
To: Andrei Zubkov <zubkov(at)moonset(dot)ru>
Cc: kuroda(dot)hayato(at)fujitsu(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Tracking statements entry timestamp in pg_stat_statements
Date: 2021-04-07 08:26:21
Message-ID: 9f927cfbea31c78bbc971c67067e8e2f@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2021-03-23 23:08 に Andrei Zubkov さんは書きました:
> Dear Kuroda,
>
>> I don't like the idea because such a column has no meaning for the
>> specific row.
>> I prefer storing timestamp if GetCurrentTimestamp() is cheap.
> I agree. New version attached.

Thanks for posting the patch.
I agree with this content.

Is it necessary to update the version of pg_stat_statements now that the
release is targeted for PG15?
We take into account the risk that users will misunderstand.

Regards,

--
Yuki Seino
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-04-07 08:27:54 Re: Truncate in synchronous logical replication failed
Previous Message Amit Langote 2021-04-07 08:18:21 Re: ModifyTable overheads in generic plans