On Thu, Apr 21, 2022 at 7:18 AM Tom Lane wrote:
> Peter Eisentraut writes:
> > 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 m
Hi,
On Thu, Apr 21, 2022 at 10:18:56AM -0400, Tom Lane wrote:
> And as for the version, if you want that you can get it from "initdb
> --version".
I assumed the point in stamping the version in the output was that
people might want to pipe it to some logfile and then later on, when
they found som
Peter Eisentraut writes:
> 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 s
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 tha
On Wed, Apr 20, 2022 at 2:04 PM Peter Eisentraut <
peter.eisentr...@enterprisedb.com> wrote:
> On 19.04.22 15:55, David G. Johnston wrote:
> > The motivating situation had me placing it as close to the last line as
> > possible so my 8 line or so tmux panel would show it to me without
> > scrollin
On 19.04.22 15:55, David G. Johnston wrote:
The motivating situation had me placing it as close to the last line as
possible so my 8 line or so tmux panel would show it to me without
scrolling. The version is all I cared about, but when writing the patch
the path seemed to be at least worth co
> On 19 Apr 2022, at 15:56, David G. Johnston
> wrote:
> The motivating situation had me placing it as close to the last line as
> possible so my 8 line or so tmux panel would show it to me without scrolling.
> The version is all I cared about, but when writing the patch the path seemed
> to
On Tue, Apr 19, 2022 at 2:28 AM Daniel Gustafsson wrote:
> > On 16 Apr 2022, at 01:50, David G. Johnston
> wrote:
>
> > initdb is already pretty chatty, and the version of the cluster being
> installed seems useful to include as well.
>
> That seems quite reasonable.
>
> > The data directory is
> On 16 Apr 2022, at 01:50, David G. Johnston
> wrote:
> initdb is already pretty chatty, and the version of the cluster being
> installed seems useful to include as well.
That seems quite reasonable.
> The data directory is probably less so - though I am thinking that the
> absolute path
Hackers,
initdb is already pretty chatty, and the version of the cluster being
installed seems useful to include as well. The data directory is probably
less so - though I am thinking that the absolute path would be useful to
report, especially when a relative path is specified (I didn't figure t
10 matches
Mail list logo
