| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Raphael Hertzog <hertzog(at)debian(dot)org> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Fails to work on live images due to fsync() on pg_commit_ts before doing any write there |
| Date: | 2017-11-08 01:42:09 |
| Message-ID: | CAB7nPqTVmtT1qT1EPgrB9z0OEUMwp1SW1XQx_ii89xqiKxe6JA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 8, 2017 at 1:23 AM, Raphael Hertzog <hertzog(at)debian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Raphael Hertzog | 2017-11-08 07:42:18 | Re: Fails to work on live images due to fsync() on pg_commit_ts before doing any write there |
| Previous Message | Michael Paquier | 2017-11-08 01:37:57 | Re: Fails to work on live images due to fsync() on pg_commit_ts before doing any write there |