| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Thomas Trenz <thomas(dot)trenz(at)jdisc(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16874: Postgres Server crashes at commit |
| Date: | 2021-03-22 05:50:19 |
| Message-ID: | YFgwG+M1DIVyJfan@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Hi Thomas,
On Mon, Feb 22, 2021 at 08:17:10AM +0100, Thomas Trenz wrote:
> just another hint. I downgraded the Postgres database to 12.6 again and I
> don't see those issues anymore in the log files on the same machine with the
> exact same configuration. Is there anything I can do to improve logging,
> check processes when using 13.2 so that you can easier isolate the root
> cause?
The issue with the WAL segment renames should be fixed by 909b449.
This will be normally available in 13.3~.
Regards,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-03-22 05:54:37 | Re: BUG #16927: Postgres can`t access WAL files |
| Previous Message | tomohiro hiramitsu | 2021-03-22 05:43:21 | Re: BUG #16722: PG hanging on COPY when table has close to 2^32 toasts in the table. |