From: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Adding extension default version to \dx |
Date: | 2025-01-14 17:11:05 |
Message-ID: | 20250115021105.4f6d7d6fb36169eac88d73fc@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 10 Jan 2025 20:37:17 +0800
Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> Hi,
>
> On Fri, Jan 10, 2025 at 01:04:14PM +0100, Magnus Hagander wrote:
> > In an effort to make at least a couple of more people realize they have to
> > run ALTER EXTENSION UPDATE after they've upgraded an extension, as well as
> > make it a bit easier to realize when you have to do it, I propose we add
> > the default version of an extension to \dx in psql.
>
> +1, I need the info very often and \dx is way faster than writing a query for
> that when I need it, especially since \dx output is not too big.
>
> > We currently show the
> > installed version in the schema, but no indications that a newer one might
> > be installed on the system.
> >
> > PFA a patch to do this.
>
> Patch LGTM, tested locally and I like the output.
I have a minor comment.
+ "LEFT JOIN pg_catalog.pg_available_extensions() ae(name, default_version, comment) ON ae.name=e.extname "
For consistency with around codes, it seems better to add a space before and after "=",
like "ae.name = e.extname".
Regards,
Yugo Nagata
--
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2025-01-14 17:33:33 | Re: Bypassing cursors in postgres_fdw to enable parallel plans |
Previous Message | Dean Rasheed | 2025-01-14 17:10:02 | Re: psql: Option to use expanded mode for various meta-commands |