| From: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | minor bug |
| Date: | 2023-01-16 18:59:33 |
| Message-ID: | CAKkG4_kUevPqbmyOfLajx7opAQk6Cvwkvx0HRcFjSPfRPTXanA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Hi,
not sure if this is known behavior.
Server version is 14.6 (Debian 14.6-1.pgdg110+1).
In a PITR setup I have these settings:
recovery_target_xid = '852381'
recovery_target_inclusive = 'false'
In the log file I see this message:
LOG: recovery stopping before commit of transaction 852381, time
2000-01-01 00:00:00+00
But:
postgres=# select * from pg_last_committed_xact();
xid | timestamp | roident
--------+-------------------------------+---------
852380 | 2023-01-16 18:00:35.054495+00 | 0
So, the timestamp displayed in the log message is certainly wrong.
Thanks,
Torsten
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitrios Apostolou | 2023-01-16 19:05:30 | Re: Why is a hash join preferred when it does not fit in work_mem |
| Previous Message | Christophe Pettus | 2023-01-16 17:57:56 | Re: No function matches the given name and argument types. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-01-16 19:08:38 | Re: Extracting cross-version-upgrade knowledge from buildfarm client |
| Previous Message | Justin Pryzby | 2023-01-16 18:53:13 | Re: Record queryid when auto_explain.log_verbose is on |