Re: temp table indexes - Mailing list pgsql-general

From Andrew Bartley
Subject Re: temp table indexes
Date
Msg-id 003b01c1cf0b$88095f30$3200a8c0@abartleypc
Whole thread Raw
In response to Re: temp table indexes  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: temp table indexes  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-general
The testing I have already done, an index is by far better in this
circumstance.

Thanks

Andrew
----- Original Message -----
From: "Bruce Momjian" <pgman@candle.pha.pa.us>
To: "Andrew Bartley" <abartley@evolvosystems.com>
Cc: <pgsql-general@postgresql.org>
Sent: Tuesday, March 19, 2002 4:19 PM
Subject: Re: [GENERAL] temp table indexes


>
> 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@candle.pha.pa.us               |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
>
>


pgsql-general by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: temp table indexes
Next
From: Bruce Momjian
Date:
Subject: Re: temp table indexes