Re: Renaming of pg_xlog and pg_clog

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Renaming of pg_xlog and pg_clog
Дата
Msg-id 0a089d6a-ff1d-88b0-5966-44bbbe5aa202@2ndquadrant.com
обсуждение исходный текст
Ответ на Renaming of pg_xlog and pg_clog  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: Renaming of pg_xlog and pg_clog  (Magnus Hagander <magnus@hagander.net>)
Re: Renaming of pg_xlog and pg_clog  (Andres Freund <andres@anarazel.de>)
Список pgsql-hackers
On 8/25/16 10:39 PM, Michael Paquier wrote:
> I am relaunching $subject as 10 development will begin soon. As far as
> I know, there is agreement that we can do something here. Among the
> different proposals I have found:
> - pg_clog renamed to pg_commit_status, pg_xact or pg_commit
> - pg_xlog renamed to pg_xjournal, pg_wal or pg_journal

If we're going to do some renaming, then I suggest we do a
mini-file-system structure under $PGDATA, like

$PGDATA/etc
$PGDATA/log
$PGDATA/run (lock files etc.)
$PGDATA/tmp
$PGDATA/var

The names of all the things under "var" could still be refined, but it's
much less likely that users will confuse data with configuration or
plain logs under that scheme.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Yury Zhuravlev
Дата:
Сообщение: Re: Why is a newly created index contains the invalidLSN?
Следующее
От: Simon Riggs
Дата:
Сообщение: Re: WAL consistency check facility