Re: Renaming of pg_xlog and pg_clog - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id 20161024182633.wslfe2ifqmzkaoje@alvherre.pgsql
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Renaming of pg_xlog and pg_clog  (Haribabu Kommi <kommi.haribabu@gmail.com>)
List pgsql-hackers
Bruce Momjian wrote:
> On Mon, Oct 24, 2016 at 11:59:42AM -0300, Alvaro Herrera wrote:

> > There is one difference though, which is that the really destructive
> > use of pg_resetxlog is the one that removes pg_xlog files.  The other
> > uses that simply set flags in the control file are not as bad -- you can
> > simply go back to what the original value was.  I think we would only
> > need the obnoxious string requirement in the most dangerous mode.

> OK, but we are going need to document that this special flag is only
> needed for certain option uses.

Perhaps, but not in too much detail; just that "users need to follow
on-screen indications" or some such would be enough.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: FSM corruption leading to errors
Next
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: Remove extra comma at end of enum list