Postgres Pro
Downloads
Home   >   mailing lists

Re: Incorrect version of initdb - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: Incorrect version of initdb
Date
Msg-id CABUevEyA1rgitEp-t81wXSur3asEQX=8Fk-Z5ok+tNqb639Ffw@mail.gmail.com
Whole thread Raw
In response to Incorrect version of initdb  (rob stone <floriparob@gmail.com>)
List pgsql-bugs
Tree view


On Wed, Sep 30, 2020 at 8:01 AM rob stone <floriparob@gmail.com> wrote:
Hello,

Installed postgresql-13 from Debian repos.

postgres@roblaptop:/usr/lib/postgresql/13/bin$ initdb -V
initdb (PostgreSQL) 12.4 (Debian 12.4-1)

This does not execute initdb from the 13 directory, it executes it from the one in the path.

If you run "./initdb -V", you should see version 13.

 


PG_VERSION is initialised as 12.

However,

postgres@roblaptop:/usr/lib/postgresql/13/bin$ createdb -V
createdb (PostgreSQL) 13.0 (Debian 13.0-2)
pg_ctl (PostgreSQL) 12.4 (Debian 12.4-1)
pg_dump (PostgreSQL) 13.0 (Debian 13.0-2)

Debian OS:- Linux roblaptop 5.8.0-2-amd64 #1 SMP Debian 5.8.10-1 (2020-
09-19) x86_64 GNU/Linux
This is just a development box.


initdb is in the postgresql-13 package, and createdb is in postgresql-client-13. Perhaps you only installed/upgraded one of them?

Since you are in debian, you should also look at using pg_createcluster instead of raw initdb. It'll set things up properly with service starting and permissions and such things automatically for you there.
 
--

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16646: systemctl stop postgresql-12 stuck
Next
From: David Rowley
Date:
Subject: Re: table partition with inheritance having current_timestamp issue if we miss range table