Re: Renaming of pg_xlog and pg_clog
От | Magnus Hagander |
---|---|
Тема | Re: Renaming of pg_xlog and pg_clog |
Дата | |
Msg-id | CABUevExt-XUkHRc-tbQHrCukY=z8_3kDcAhc05_fULfF9q-Fzg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Renaming of pg_xlog and pg_clog (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>) |
Ответы |
Re: Renaming of pg_xlog and pg_clog
Re: Renaming of pg_xlog and pg_clog |
Список | pgsql-hackers |
<p dir="ltr"><p dir="ltr">On Aug 26, 2016 5:54 PM, "Peter Eisentraut" <<a href="mailto:peter.eisentraut@2ndquadrant.com">peter.eisentraut@2ndquadrant.com</a>>wrote:<br /> ><br /> > On 8/25/1610:39 PM, Michael Paquier wrote:<br /> > > I am relaunching $subject as 10 development will begin soon. As faras<br /> > > I know, there is agreement that we can do something here. Among the<br /> > > different proposalsI have found:<br /> > > - pg_clog renamed to pg_commit_status, pg_xact or pg_commit<br /> > > - pg_xlogrenamed to pg_xjournal, pg_wal or pg_journal<br /> ><br /> > If we're going to do some renaming, then I suggestwe do a<br /> > mini-file-system structure under $PGDATA, like<br /> ><br /> > $PGDATA/etc<br /> > $PGDATA/log<br/> > $PGDATA/run (lock files etc.)<br /> > $PGDATA/tmp<br /> > $PGDATA/var<br /> ><br /> > Thenames of all the things under "var" could still be refined, but it's<br /> > much less likely that users will confusedata with configuration or<br /> > plain logs under that scheme<p dir="ltr">Interesting idea. I worry a bit thatthis might encourage distributions to split it up into different places though, and I'm not sure we want to encouragethat.. <p dir="ltr">/Magnus
В списке pgsql-hackers по дате отправления: