On Wed, Nov 8, 2017 at 1:23 AM, Raphael Hertzog <hertzog@debian.org> wrote:
> Well, it's the case by default with no persistence. But some users enable
> persistence and then it's no longer a tmpfs which is used.
>
> The problem also exists when you enable persistence but start with an
> empty upper layer so disabling fsyncs is not really an option.
Raphaël, don't you have problems with pg_twophase as well? Wouldn't
the new fsync call in CheckPointTwoPhase() fail equally if no 2PC
transactions have happened in a checkpoint cycle? That would not be an
issue with pg_commit_ts and pg_xact normally, but we are talking about
checkpoints skipped or not depending on WAL activity, tracking which
is more properly done in v10.
--
Michael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
