Re: Add version and data directory to initdb output

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add version and data directory to initdb output
Date: 2022-04-21 12:15:41
Message-ID: d01f4561-d3c2-d83b-ad03-6c9789430eb6@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 20.04.22 23:21, David G. Johnston wrote:
> I agree with the observation but it initdb is fast enough and
> non-interactive and so that order isn't particularly appealing.

I'm not a particular fan of the current initdb output and it could use a
general revision IMO. If you want to look into that, please do. But
for your particular proposed addition, let's put it somewhere it makes
sense either in the current scheme or a future scheme when that is done.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2022-04-21 13:42:44 Re: Postgres perl module namespace
Previous Message Robert Haas 2022-04-21 12:00:30 Re: Re: fix cost subqueryscan wrong parallel cost