From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Andrew Bartley <abartley(at)evolvosystems(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: temp table indexes |
Date: | 2002-03-19 05:19:19 |
Message-ID: | 200203190519.g2J5JJP07859@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Read FAQ item 4.8 --- new version on web site. It explains index is not
always the best.
---------------------------------------------------------------------------
Andrew Bartley wrote:
> Hi,
>
> We are using Postgres 7.1.3.
>
> I am trying to get postgres to use an index that is created on a temp table. The temp table and index is created and loaded from within a plpgsql proc. The select I am trying to force a keyed select on, is also in the same proc.
>
> I have tired SET ENABLE_SEQSCAN TO Off But it still does table scans.
>
> If I create the same temp table from an odbc driven windows sql app like WinSQL lite, I can force an index read if I vacuum the temp table once loaded. I have tired vacuuming the table from within the plpgsql proc, but that seems to cause postgres to shut down.
>
> Can anyone help me here?
>
> Thanks
>
> Andrew
>
>
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-03-19 05:59:54 | Re: temp table indexes |
Previous Message | Tom Lane | 2002-03-19 04:21:41 | Re: Performance issues |