From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Postgresql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: feature request: show pgsql version when running initdb |
Date: | 2003-09-26 15:22:43 |
Message-ID: | 3F7459C3.7000506@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>"Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
>
>
>>Moral of the story, if it's in your path first then it's the default and you
>>should therefore be happy with the results or be prepared to live with them,
>>otherwise make sure what you're running.
>>
>>
>
>I would think that having initdb print its version while running would
>be in the category of "too late to help" anyway. Making a habit of
>running "initdb --version" in advance seems like much the better way
>to proceed, if this is a problem for you.
>
>Personally I've never had such a mistake occur, even though I normally
>have several different PG installations active on my development
>machines. I think this is because I always set PATH, PGPORT, and PGDATA
>consistently --- rather than manipulating them by hand, I have little
>scripts that I run to make one installation or another the "active" one.
>
>
It might make sense to have the version explicitly reported by
show_setting/debug modes - the change would be entirely trivial and not
very intrusive to general use.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-09-26 15:30:59 | Re: invalid tid errors in latest 7.3.4 stable. |
Previous Message | Matthew T. O'Connor | 2003-09-26 15:17:25 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |