Re: Renaming of pg_xlog and pg_clog
От | Jim Nasby |
---|---|
Тема | Re: Renaming of pg_xlog and pg_clog |
Дата | |
Msg-id | d42ab8e1-8573-abf3-f63a-1301c46aedd9@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: Renaming of pg_xlog and pg_clog (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Renaming of pg_xlog and pg_clog
Re: Renaming of pg_xlog and pg_clog Re: Renaming of pg_xlog and pg_clog |
Список | pgsql-hackers |
On 8/26/16 4:08 PM, Andres Freund wrote: > Splitting of ephemeral data seems to have a benefit, the rest seems more > like rather noisy busywork to me. People accidentally blowing away pg_clog or pg_xlog is a pretty common occurrence, and I don't think there's all that many tools that reference them. I think it's well worth renaming them. I actually like the idea of re-organizing everything too. It would be easy to include a tool that puts symlinks in place to all the original locations if you need that. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
В списке pgsql-hackers по дате отправления: