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

Поиск
Список
Период
Сортировка
Искать

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

От:
PG Bug reporting form <noreply@postgresql.org>
Дата:
The following bug has been logged on the website:

Bug reference:      19739
Logged by:          Shallow
Email address:      theshallow27@gmail.com
PostgreSQL version: 18.6
Operating system:   Linux
Description:        

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. The same query without parameters
returns equality. Parameterized execution uses the extended query protocol,
so
this may expose a distinction between Parse/Bind/Execute message timing and
the documented “first statement” guarantee.

**Reproduction:** Using Psycopg with autocommit enabled on a fresh
connection:

```python
cur.execute(
    "SELECT transaction_timestamp() = statement_timestamp() WHERE %s::int =
0",
    (0,),
)
print(cur.fetchone())  # (False,)
```

Control query on a fresh autocommit connection:

```sql
SELECT transaction_timestamp() = statement_timestamp(); -- true
```

**Expected result:** The parameterized query, as the first SQL statement in
an
implicit transaction, should return `true`; alternatively, the documentation
should clarify how extended-protocol messages affect the guarantee.




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

От:
Tom Lane <tgl@sss.pgh.pa.us>
Дата:
PG Bug reporting form  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


FAQ