From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: transction_timestamp() inside of procedures
Date: Wed, 26 Sep 2018 10:07:03 -0400
Message-ID: <23174.1537970823@sss.pgh.pa.us> (raw)
In-Reply-To: <20180926125207.GA10161@momjian.us>
References: <20180920234040.GC29981@momjian.us>
<20180921045536.GJ1338@paquier.xyz>
<20180921051206.bzfiew4nthmunpbj@alap3.anarazel.de>
<20180921053425.GM1338@paquier.xyz>
<20180921102822.GA22699@momjian.us>
<20180921223502.GA18319@momjian.us>
<d2e75a46-a8af-e9f4-0106-609068e9c3f8@2ndquadrant.com>
<20180926125207.GA10161@momjian.us>
Bruce Momjian <bruce@momjian.us> writes:
> On Wed, Sep 26, 2018 at 02:38:25PM +0200, Peter Eisentraut wrote:
>> We could certainly address this by adding three or four or five new
>> timestamps that cover all these varieties. But perhaps it's worth
>> asking what these timestamps are useful for and which ones we really need.
> Frankly, we might be fine with just documenting it and see if anyone
> complains.
I'm not for adding a bunch of new action-start timestamps without very
clear use-cases for them, because each one we add means more gettimeday()
overhead that might or might not ever be useful.
I agree that it would be surprising for transaction timestamp to be newer
than statement timestamp. So for now at least, I'd be satisfied with
documenting the behavior.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, bruce@momjian.us, peter.eisentraut@2ndquadrant.com, michael@paquier.xyz, andres@anarazel.de
Subject: Re: transction_timestamp() inside of procedures
In-Reply-To: <23174.1537970823@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox