Re: BUG #15589: Due to missing wal, restore ends prematurely and opens database for read/write

From: leif(at)lako(dot)no
To: "Kyotaro HORIGUCHI" <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15589: Due to missing wal, restore ends prematurely and opens database for read/write
Date: 2019-02-22 08:49:38
Message-ID: 4580ce9139ea70b42946f7a5d6e1c713@lako.no
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

"Kyotaro HORIGUCHI" <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> skrev 31. januar 2019 kl. 13:28:

> If this is acceptable I'll post complete version (including
> documentation). I don't think this back-patcheable.
>

If you are asking me, then I think this is exactly what I wanted, thank you for your effort.

>> With large databases and a lot of wal-files it is time consuming to repeat parts of the process.
>
> I understand your concern.
>
> regards.
>
> --
> Kyotaro Horiguchi
> NTT Open Source Software Center

regards
Leif Gunnar Erlandsen

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Maksim Milyutin 2019-02-22 12:37:51 Re: BUG #15638: pg_basebackup with --wal-method=stream incorrectly generates WAL segment created during backup
Previous Message PG Bug reporting form 2019-02-22 08:45:41 BUG #15650: oracle_fdw issue

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2019-02-22 09:14:33 Re: Unnecessary checks for new rows by some RI trigger functions?
Previous Message Matsumura, Ryo 2019-02-22 08:49:10 RE: SQL statement PREPARE does not work in ECPG