Re: pg_upgarde: The control data check for equal max_index_keys in old and new version

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: neha khatri <nehakhatri5(at)gmail(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: pg_upgarde: The control data check for equal max_index_keys in old and new version
Date: 2016-04-22 03:45:47
Message-ID: 19574.1461296747@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

neha khatri <nehakhatri5(at)gmail(dot)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

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message neha khatri 2016-04-22 04:30:37 Re: pg_upgarde: The control data check for equal max_index_keys in old and new version
Previous Message neha khatri 2016-04-22 03:26:13 pg_upgarde: The control data check for equal max_index_keys in old and new version