Re: Checkpoints stuck after a failed bulk write inside a savepoint

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Joao Rito <joaovictor(dot)rito(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Checkpoints stuck after a failed bulk write inside a savepoint
Date: 2026-11-16 17:20:36
Message-ID: CAGRkXqRDyvVxe_DoJrW4iqDYbdUNGqt83PHB7y0VZAuyUN=xSQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Joao,

Thanks for testing

> I assume that costs
> at most one extra fsync in a checkpoint, but I did not measure it.

Yes, the cost is one extra fsync per segment on a file we just
flushed. It only happens when a checkpoint runs during the bulk write.

Thanks,
Shihao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kirill Reshke 2026-11-16 17:30:22 Re: contain_nonstrict_functions_walker() fails to consider JsonExpr and CoerceToDomain
Previous Message Sami Imseih 2026-11-16 16:56:09 Re: pgstat: Flush some statistics within running transactions, take 2