Horton

Re: Adding extension default version to \dx

Yugo Nagata <nagata@sraoss.co.jp>

View thread
From: Yugo Nagata <nagata@sraoss.co.jp>
To: Julien Rouhaud <rjuju123@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2025-01-14T17:11:05Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. psql: use consistent alias for pg_description

  2. psql: show default extension version in \dx output

On Fri, 10 Jan 2025 20:37:17 +0800
Julien Rouhaud <rjuju123@gmail.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@sraoss.co.jp>