Re: BUG #19739: Parameterized first autocommit statement can have different `transaction_timestamp()` and `statement - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19739: Parameterized first autocommit statement can have different `transaction_timestamp()` and `statement
Date
Msg-id 261446.1791064732@sss.pgh.pa.us
Whole thread
In response to BUG #19739: Parameterized first autocommit statement can have different `transaction_timestamp()` and `statement  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19742: `INTERSECT` under a `UNION ALL` with an empty arm fails with "could not find pathkey item t"
Next
From: Tom Lane
Date:
Subject: Re: BUG #19742: `INTERSECT` under a `UNION ALL` with an empty arm fails with "could not find pathkey item t"