Re: [HACKERS] Fix up for BTP_CHAIN problems

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Wayne Piekarski <wayne(at)senet(dot)com(dot)au>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Fix up for BTP_CHAIN problems
Date: 1999-07-19 02:06:46
Message-ID: 37928836.2D933F6A@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> > Would a solution to the problem be to automatically include the row OID
> > when creating an index?
>
> Vadim had muttered about doing something like that as a substitute for
> fixing the equal-keys logic, but it seems like a kluge to me, especially
> if it makes the index bigger. (OTOH I think he was envisioning using
> some already-existing field of index tuple headers as the tiebreaker,
> so maybe it wouldn't cost any space.)

It will increase size of index tuples on inner pages, but not
on leaf ones.

Vadim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-07-19 02:41:25 Please add to 6.5.1
Previous Message Vadim Mikheev 1999-07-19 01:56:24 Re: [HACKERS] Fix up for BTP_CHAIN problems