Re: pg_upgarde: The control data check for equal max_index_keys in old and new version - Mailing list pgsql-novice

From Tom Lane
Subject Re: pg_upgarde: The control data check for equal max_index_keys in old and new version
Date
Msg-id 19574.1461296747@sss.pgh.pa.us
Whole thread Raw
In response to pg_upgarde: The control data check for equal max_index_keys in old and new version  (neha khatri <nehakhatri5@gmail.com>)
Responses Re: pg_upgarde: The control data check for equal max_index_keys in old and new version
List pgsql-novice
neha khatri <nehakhatri5@gmail.com> writes:
> I have recently started working on Postgresql and I was looking in the the
> pg_upgrade code. pg_upgrade checks index control data(max_index_keys) to be
> equal in the old and new version.

> I would like to understand why the number of index columns should be equal
> in new and old versions.

Because that changes the size of index tuple headers, see
src/include/access/itup.h

> Can the number of maximum index columns not be
> changed from one release to another release.

Sure, as long as you don't care about on-disk database compatibility.
The checks associated with pg_control are meant to ensure exactly
that, though.

            regards, tom lane


pgsql-novice by date:

Previous
From: neha khatri
Date:
Subject: pg_upgarde: The control data check for equal max_index_keys in old and new version
Next
From: neha khatri
Date:
Subject: Re: pg_upgarde: The control data check for equal max_index_keys in old and new version