| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add docs stub for recovery.conf |
| Date: | 2020-12-03 00:33:12 |
| Message-ID: | CAKFQuwYgXFh7CewdXxiBfy09Z+7Tx7adyJAKejX3Wu_UsM-ZWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 2, 2020 at 5:26 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I think the ideal solution is to create a section for all the rename
> cases and do all the redirects to that page. The page would list the
> old and new name for each item, and would link to the section for each
> new item.
>
>
Nothing prevents us from doing that for simple renames. For me, this
situation is not a simple rename and the proposed solution is appropriate
for what it is - changing the implementation details of an existing
feature. We can do both - though the simple rename page doesn't seem
particularly appealing at first glance.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tsunakawa.takay@fujitsu.com | 2020-12-03 00:54:56 | RE: Deprecate custom encoding conversions |
| Previous Message | Bruce Momjian | 2020-12-03 00:26:58 | Re: Add docs stub for recovery.conf |