Re: Renaming of pg_xlog and pg_clog

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: Renaming of pg_xlog and pg_clog
Дата
Msg-id CAM-w4HNw4FvashNFnSBAiybyLmieiZDNyHBEYrPrvi78vgqjNQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Renaming of pg_xlog and pg_clog  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: Renaming of pg_xlog and pg_clog  (Bruce Momjian <bruce@momjian.us>)
Список 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 по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: On conflict update & hint bits
Следующее
От: Venkata B Nagothi
Дата:
Сообщение: pg_xlog error on the master