All,
I can see why the query below is slow. The lead table is 34 million rows,
and a sequential scan always takes 3+ minutes. Mailing_id is the PK for
mailing and is constrained as a foreign key (NULLS allowed) in lead.
There is an index on lead.mailing_id. I've just run VACUUM ANALYZE on
lead
On Fri, Oct 14, 2005 at 06:02:56PM +0200, [EMAIL PROTECTED] wrote:
> Ok, since my question got no answer on the general list, I'm reposting
> it here since this list seems in fact better suited to it.
>
> Does anyone here know what is the most efficient way to list all
> different values of a
On Fri, Oct 14, 2005 at 06:02:56PM +0200, [EMAIL PROTECTED] wrote:
> Does anyone here know what is the most efficient way to list all
> different values of a given column with low cardinality ? For instance
> I have a table with columns DAY, NAME, ID, etc. The table is updated
> about each wee
Ok, since my question got no answer on the general list, I'm reposting
it here since this list seems in fact better suited to it.
Does anyone here know what is the most efficient way to list all
different values of a given column with low cardinality ? For instance
I have a table with columns
Nörder-Tuitje wrote:
Hi,
meanwhile I have received the hint to make postgres use the index via
SET ENABLE_SEQSCAN=FALSE;
which fits perfectly. The execution plan now indicates full use of
index.
What execution plan? I still only see one message on the list.
Nevertheless this is merely a w
Hi,
meanwhile I have received the hint to make postgres use the index via
SET ENABLE_SEQSCAN=FALSE;
which fits perfectly. The execution plan now indicates full use of index.
Nevertheless this is merely a workaround. Maybe the io-costs are configured to
cheap.
thanks :-)
-Ursprüngliche N
Yes I did, and it works better(on a test server). I had no time to put it in
production.
I will try to do small steps to see what happens.
Regards,
Andy.
- Original Message -
From: "Andrew Sullivan" <[EMAIL PROTECTED]>
To:
Sent: Thursday, October 13, 2005 6:01 PM
Subject: Re: [PERFO
