Re: please define 'statement' in the glossary
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, petermittere@gmail.com,
pgsql-docs@lists.postgresql.org
Date: 2025-07-14T16:08:46Z
Lists: pgsql-docs
"David G. Johnston" <david.g.johnston@gmail.com> writes: > Cannot readily test this presently but I wonder what the following produces: > psql -c "begin; select statement_timestamp(), transaction_timestamp(); > select statement_timestamp(), transaction_timestamp(); commit; begin; > select statement_timestamp(), transaction_timestamp(); commit;" > Transaction timestamp should progress while statement timestamp should not, > right? AFAICT neither one progresses. I think the reason is that (1) statement timestamp is set by arrival of the command message and (2) transaction timestamp is set by copying statement timestamp at the moment of beginning a transaction. regards, tom lane
Commits
-
Doc: clarify description of current-date/time functions.
- 0e2cc385b97e 13.22 landed
- 209a22d794d5 14.19 landed
- 5ea9d9ac0c33 15.14 landed
- 2e7390928e80 16.10 landed
- bdb052f53b1a 17.6 landed
- c33e55ac91d2 18.0 landed
- 8ffd9ac3b206 19 (unreleased) landed
-
Some editorial work on the documentation of the current-date/time
- eaf8f312c754 8.2.0 cited