Re: BUG #19739: Parameterized first autocommit statement can have different `transaction_timestamp()` and `statement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: theshallow27(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19739: Parameterized first autocommit statement can have different `transaction_timestamp()` and `statement
Date: 2026-10-03 21:58:52
Message-ID: 261446.1791064732@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Tom Lane 2026-10-03 21:53:48 Re: BUG #19742: `INTERSECT` under a `UNION ALL` with an empty arm fails with "could not find pathkey item t"