Re: Database-level collation version tracking - Mailing list pgsql-hackers

From Michael Banck
Subject Re: Database-level collation version tracking
Date
Msg-id 6202796c.1c69fb81.2ee8a.903d@mx.google.com
Whole thread Raw
In response to Re: Database-level collation version tracking  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
List pgsql-hackers
On Mon, Feb 07, 2022 at 04:44:24PM +0100, Peter Eisentraut wrote:
> On 07.02.22 11:29, Julien Rouhaud wrote:
> > - that's not really something new with this patch, but should we output the
> >    collation version info or mismatch info in \l / \dO?
> 
> It's a possibility.  Perhaps there is a question of performance if we show
> it in \l and people have tons of databases and they have to make a locale
> call for each one.  As you say, it's more an independent feature, but it's
> worth looking into.

Ok, but \l+ shows among others the database size, so I guess at that
level also showing this should be fine? (or is that already the case?)


Michael



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Improve correlation names in sanity tests
Next
From: Andrew Dunstan
Date:
Subject: Re: [RFC] building postgres with meson - perl embedding