Re: transction_timestamp() inside of procedures - Mailing list pgsql-hackers

From Daniel Verite
Subject Re: transction_timestamp() inside of procedures
Date
Msg-id 426715fa-0dd7-4826-b079-1426ca8e6f12@manitou-mail.org
Whole thread Raw
In response to Re: transction_timestamp() inside of procedures  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: transction_timestamp() inside of procedures
List pgsql-hackers
    Tom Lane wrote:

> I agree that it would be surprising for transaction timestamp to be newer
> than statement timestamp.

To me it's more surprising to start a new transaction and having
transaction_timestamp() still pointing at the start of a previous
transaction.
This feels like a side-effect of being spawned by a procedure,
and an exception to what transaction_timestamp() normally means
or meant until now.

OTOH transaction_timestamp() being possibly newer than
statement_timestamp() seems like a normal consequence of
transactions being created intra-statement.

+1 for transaction_timestamp() and pg_stat_activity being updated
to follow intra-procedure transactions.


Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Allowing printf("%m") only where it actually works
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Remove absolete function TupleDescGetSlot().