Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work
Date: 2022-01-19 22:53:43
Message-ID: 773619.1642632823@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Bossart, Nathan" <bossartn(at)amazon(dot)com> writes:
> I think the other side of this is that we don't want checkpointing to
> continually fail because of a noncritical failure. That could also
> lead to problems down the road.

Yeah, a persistent failure to complete checkpoints is very nasty.
Your disk will soon fill with unrecyclable WAL. I don't see how
that's better than a somewhat hypothetical performance issue.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2022-01-20 00:05:40 Re: pg_upgrade should truncate/remove its logs before running
Previous Message Bossart, Nathan 2022-01-19 22:48:18 Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work