Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal
От | Michael Paquier |
---|---|
Тема | Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal |
Дата | |
Msg-id | CAB7nPqSEe_T=YpO_0NyvdV2DsQQZu=JmUsY7+RMo9d1iSGutqQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal (Vladimir Rusinov <vrusinov@google.com>) |
Ответы |
Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal
|
Список | pgsql-hackers |
On Fri, Dec 30, 2016 at 8:08 PM, Vladimir Rusinov <vrusinov@google.com> wrote: > Now, I'm not sure whether it is worth maintaining function aliases. Assuming > these are indeed trivial (can somebody point me to example?) I see roughly > the same amount of downsides both ways. > Having aliases raises additional questions: > - do we keep them documented (probably not?) > - do we keep them forever or kill in some future version? The idea here is to keep documented only the new function names, but mention in the release notes that aliases are kept, and that those will be dropped in a couple of years (see for example 5d58c07a for initdb). This will give plenty of time to monitoring script maintainers to adapt to the new world order. -- Michael
В списке pgsql-hackers по дате отправления: