From: Tom Lane <tgl@sss.pgh.pa.us>
To: theshallow27@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19739: Parameterized first autocommit statement can have
 different `transaction_timestamp()` and `statement
In-reply-to: <19739-bdca3e8fd9b496fa@postgresql.org>
References: <19739-bdca3e8fd9b496fa@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Fri, 02 Oct 2026 22:37:31 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <261445.1791064732.1@sss.pgh.pa.us>
Date: Sat, 03 Oct 2026 17:58:52 -0400
Message-ID: <261446.1791064732@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/261446.1791064732%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> The documentation says `transaction_timestamp()` and
> `statement_timestamp()` return the same value during the first statement of
> a
> transaction. With a parameterized query executed as the first command on a
> fresh autocommit connection, they differ.

Strictly speaking, that depends on which steps of an extended-protocol
query count as separate statements.  But I don't think we're going to
modify this documentation to dive into details as abstruse as that;
it would merely confuse the same people the comment is meant to help.

			regards, tom lane