Re: pg_replslotdata - a tool for displaying replication slot information
От | Bossart, Nathan |
---|---|
Тема | Re: pg_replslotdata - a tool for displaying replication slot information |
Дата | |
Msg-id | 4D880281-2732-493A-B189-5390E3772973@amazon.com обсуждение исходный текст |
Ответ на | Re: pg_replslotdata - a tool for displaying replication slot information (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: pg_replslotdata - a tool for displaying replication slot information
|
Список | pgsql-hackers |
On 12/5/21, 11:10 PM, "Michael Paquier" <michael@paquier.xyz> wrote: > On Thu, Dec 02, 2021 at 08:32:08AM +0530, Bharath Rupireddy wrote: >> On Thu, Dec 2, 2021 at 4:22 AM Andres Freund <andres@anarazel.de> wrote: >>>> I don't have any other compelling use- cases at the moment, but I will say >>>> that it is typically nice from an administrative standpoint to be able to >>>> inspect things like this without logging into a running server. >>> >>> Weighed against the cost of maintaining (including documentation) a separate >>> tool this doesn't seem sufficient reason. >> >> IMHO, this shouldn't be a reason to not get something useful (useful >> IMO and few others in this thread) into the core. The maintenance of >> the tools generally is low compared to the core server features once >> they get reviewed and committed. > > Well, a bit less maintenance is always better than more maintenance. > An extra cost that you may be missing is related to the translation of > the documentation, as well as the translation of any new strings this > would require. FWIW, I don't directly see a use for this tool that > could not be solved with an online server. Bharath, perhaps you should maintain this outside of core PostgreSQL for now. If some compelling use-cases ever surface that make it seem worth the added maintenance burden, this thread could probably be revisited. Nathan
В списке pgsql-hackers по дате отправления: