| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | TipTop Labs <office(at)tiptop-labs(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14999: pg_rewind corrupts control file global/pg_control |
| Date: | 2018-06-19 07:09:56 |
| Message-ID: | 20180619070956.GB31737@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Mon, Apr 09, 2018 at 01:58:26PM +0900, Michael Paquier wrote:
> That's mentioned in the docs of the attached.
So, I have read again this thread, and it seems to me that there are
many approaches, but all of them have downsides. Hence at the end I
would suggest to document the limitation with for example the attached,
and call it a day.
Thoughts?
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Add-note-in-pg_rewind-documentation-about-read-only-.patch | text/x-diff | 4.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hemin | 2018-06-19 07:56:15 | Re: When pg_rewind success, the database can't startup |
| Previous Message | Michael Paquier | 2018-06-19 06:59:40 | Re: When pg_rewind success, the database can't startup |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-06-19 07:27:08 | Re: Partitioning with temp tables is broken |
| Previous Message | Andres Freund | 2018-06-19 06:30:28 | Re: Excessive CPU usage in StandbyReleaseLocks() |