| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fix a typo in pg_rotate_logfile |
| Date: | 2024-02-14 13:35:39 |
| Message-ID: | B07CC211-DE35-4AC5-BD4E-0C6466700B06@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 14 Feb 2024, at 11:35, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> That said, pgAdmin III has been out of support for many years, and as far as I know, it (and similarly old versions of EDB's PEM which was based on it) were the only consumers of adminpack. I would not be sad to see it removed entirely
Searching on Github and Debian Codesearch I cannot find any reference to anyone
using any function from adminpack. With pgAdminIII being EOL it might be to
remove it now rather than be on the hook to maintain it for another 5 years
until v17 goes EOL. It'll still be around for years in V16->.
If anyone still uses pgAdminIII then I have a hard time believing they are
diligently updating to the latest major version of postgres..
Attached is a diff to show what it would look like to remove adminpack (catalog
version bump omitted on purpose to avoid conflicts until commit).
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Remove-the-adminpack-extension.patch | application/octet-stream | 43.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2024-02-14 13:56:15 | Re: Synchronizing slots from primary to standby |
| Previous Message | Tomas Vondra | 2024-02-14 13:34:40 | Re: index prefetching |