Re: bug on log generation ?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug on log generation ?
Date: 2022-08-08 16:02:04
Message-ID: 20220808160204.owjxz2eb234fba3k@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-08-08 10:32:22 -0400, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > What platform is this on? Is it possible that on some platform the chunk
> > size we're using is not doing an atomic write?
>
> Another idea is that some of the write() calls are failing --- elog.c
> doesn't check for that.

I was suspicious of those as well. It might be a good idea to at least write
such failures to stderr, otherwise it's just about impossible to debug. Not
that stderr will always point anywhere useful...

I can imagine that a system under heavy memory pressure might fail writing, if
there's a lot of writes in a row or such.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2022-08-08 16:08:09 Re: make update-po@master stops at pg_upgrade
Previous Message Önder Kalacı 2022-08-08 15:58:52 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher