Обсуждение: Meaning of "pg_control version number:"
Hi,
I supposed "pg_control version number:" is related to pg version, but fresh pg 15 instance pg_controldata shows 1300:
$ initdb -V
initdb (PostgreSQL) 15.1
$ initdb
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /pgdata/pgsql/15/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Europe/Tallinn
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
Success. You can now start the database server using:
pg_ctl -D /pgdata/pgsql/15/data -l logfile start
$ pg_controldata -V
pg_controldata (PostgreSQL) 15.1
$ pg_controldata /pgdata/pgsql/15/data | grep "pg_control version number:"
pg_control version number: 1300
I supposed "pg_control version number:" is related to pg version, but fresh pg 15 instance pg_controldata shows 1300:
$ initdb -V
initdb (PostgreSQL) 15.1
$ initdb
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.
The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".
Data page checksums are disabled.
fixing permissions on existing directory /pgdata/pgsql/15/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Europe/Tallinn
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok
initdb: warning: enabling "trust" authentication for local connections
initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
Success. You can now start the database server using:
pg_ctl -D /pgdata/pgsql/15/data -l logfile start
$ pg_controldata -V
pg_controldata (PostgreSQL) 15.1
$ pg_controldata /pgdata/pgsql/15/data | grep "pg_control version number:"
pg_control version number: 1300
br
Kaido
On Friday, January 13, 2023, kaido vaikla <kaido.vaikla@gmail.com> wrote:
Hi,
I supposed "pg_control version number:" is related to pg version, but fresh pg 15 instance pg_controldata shows 1300:
David J.
"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Friday, January 13, 2023, kaido vaikla <kaido.vaikla@gmail.com> wrote: >> I supposed "pg_control version number:" is related to pg version, but >> fresh pg 15 instance pg_controldata shows 1300: > https://github.com/postgres/postgres/blob/master/src/include/catalog/pg_control.h We only move that value when the format of pg_control actually changes. So in this case you can see it's been stable since v13. regards, tom lane
Clear, thnx Tom
br
Kaido
br
Kaido
On Fri, 13 Jan 2023 at 16:50, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Friday, January 13, 2023, kaido vaikla <kaido.vaikla@gmail.com> wrote:
>> I supposed "pg_control version number:" is related to pg version, but
>> fresh pg 15 instance pg_controldata shows 1300:
> https://github.com/postgres/postgres/blob/master/src/include/catalog/pg_control.h
We only move that value when the format of pg_control actually changes.
So in this case you can see it's been stable since v13.
regards, tom lane
Hi
Could you please take this email of your list.
Sent from my Galaxy
-------- Original message --------
From: kaido vaikla <kaido.vaikla@gmail.com>
Date: 13/01/2023 15:49 (GMT+00:00)
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, pgsql-admin@postgresql.org
Subject: Re: Meaning of "pg_control version number:"
Clear, thnx Tom
br
Kaido
br
Kaido
On Fri, 13 Jan 2023 at 16:50, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:
> On Friday, January 13, 2023, kaido vaikla <kaido.vaikla@gmail.com> wrote:
>> I supposed "pg_control version number:" is related to pg version, but
>> fresh pg 15 instance pg_controldata shows 1300:
> https://github.com/postgres/postgres/blob/master/src/include/catalog/pg_control.h
We only move that value when the format of pg_control actually changes.
So in this case you can see it's been stable since v13.
regards, tom lane