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

From Greg Stark
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id CAM-w4HNw4FvashNFnSBAiybyLmieiZDNyHBEYrPrvi78vgqjNQ@mail.gmail.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Renaming of pg_xlog and pg_clog  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Fri, Oct 21, 2016 at 9:03 PM, Stephen Frost <sfrost@snowman.net> wrote:
> WARNING: The following essential packages will be removed.
> This should NOT be done unless you know exactly what you are doing!
>   login
> 0 upgraded, 0 newly installed, 1 to remove and 71 not upgraded.
> After this operation, 1,212 kB disk space will be freed.
> You are about to do something potentially harmful.
> To continue type in the phrase 'Yes, do as I say!'

Another case was:  glxgears -iacknowledgethatthistoolisnotabenchmark

Which was required to get it to print the FPS for a while. The problem
-- and also the advantage -- of this is that it's scriptable. That
means people can still put it in recipe books and scripts and others
can copy it without being aware what it does or even that they're
doing it.

I think the apt-get behaviour was specifically designed to ensure it
couldn't easily be put into a script which I would have said was
desirable -- except I suspect there are situations where Postgres
database scripts need to do a resetxlog. I'm not sure I can think of
any examples offhand but I wouldn't be too surprised.



-- 
greg



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: On conflict update & hint bits
Next
From: Venkata B Nagothi
Date:
Subject: pg_xlog error on the master