Re: Moving the vacuum GUCs' docs out of the Client Connection Defaults section
От | Daniel Gustafsson |
---|---|
Тема | Re: Moving the vacuum GUCs' docs out of the Client Connection Defaults section |
Дата | |
Msg-id | 5C20F2F0-FBF6-47C4-B0A3-A0760127C946@yesql.se обсуждение исходный текст |
Ответ на | Re: Moving the vacuum GUCs' docs out of the Client Connection Defaults section (Melanie Plageman <melanieplageman@gmail.com>) |
Список | pgsql-hackers |
> On 9 Jan 2025, at 02:30, Melanie Plageman <melanieplageman@gmail.com> wrote: > > On Wed, Jan 8, 2025 at 6:35 AM Daniel Gustafsson <daniel@yesql.se> wrote: >> >>> On 7 Jan 2025, at 21:14, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> >>> I might be wrong, but I had the idea that our docs website has a >>> capability to provide such redirects. You'd probably need to ask >>> about that on the pgsql-www list, unless somebody who knows the >>> answer notices this thread. >> >> There is functionality in pgweb to provide a page alias for whenever a page is >> renamed to keep the links to other versions working. One example is: >> >> https://www.postgresql.org/docs/9.4/catalog-pg-replication-slots.html >> https://www.postgresql.org/docs/17/view-pg-replication-slots.html >> >> There is also a redirect functionality, which isn't used anywhere right now, >> but ideally could be used to redirect bookmarks for /current/<oldname> to >> /current/<newname>. > > Thanks to Nathan and Tom for noticing and Daniel for replying. So, if > I understand correctly, pgweb will do this for me without me needing > to do anything in my patch? Correct, it's a setting in the database on the postgresql.org website. -- Daniel Gustafsson
В списке pgsql-hackers по дате отправления: