Re: global.bki vs template1.bki init files

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: global.bki vs template1.bki init files
Date: 2001-06-12 01:14:03
Message-ID: 200106120114.f5C1E3o08658@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

]> > I thought we agreed to merge them already.
>
> We did? Good. Will make it so.

I know Peter mentioned it a long time ago.

> > Also, could we modify
> > IndexScanOK() to catch this case and do a heap scan?
>
> How? Also, why?

I remember problems getting the index on pg_index because of recursive
lookups so I thought you could either have bootstrap mode ignore the
pg_shadow index or have recursion identified and fallback to heapscan,
but if you merge them there isn't much point.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alex Pilosov 2001-06-12 01:29:39 [PATCH] addition of text_inet, text_cidr and inet_set_masklen
Previous Message Tom Lane 2001-06-12 01:10:54 Re: global.bki vs template1.bki init files