| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: minor bug |
| Date: | 2023-01-17 10:12:33 |
| Message-ID: | Y8Z0kdngRAc++wga@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Tue, Jan 17, 2023 at 10:42:03AM +0100, Laurenz Albe wrote:
> If recovery stops at a WAL record that has no timestamp, you get this
> bogus recovery stop time. I think we should show the recovery stop time
> only if time was the target, as in the attached patch.
Good catch! I'll try to take a look.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wiwwo Staff | 2023-01-17 14:48:58 | Tablespace OID, database OID, relfilenode |
| Previous Message | Laurenz Albe | 2023-01-17 09:42:03 | Re: minor bug |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-01-17 10:26:54 | Re: ExecRTCheckPerms() and many prunable partitions (checkAsUser) |
| Previous Message | Amit Kapila | 2023-01-17 10:04:02 | Re: Logical replication timeout problem |