Re: Index usage for BYTEA column in OR/IN clause

From: David Garamond <lists(at)zara(dot)6(dot)isreserved(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruno Wolff III <bruno(at)wolff(dot)to>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Index usage for BYTEA column in OR/IN clause
Date: 2004-03-29 04:43:23
Message-ID: 4067A96B.4080204@zara.6.isreserved.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Tom Lane wrote:
> This script is lacking a VACUUM or ANALYZE command, so the planner
> doesn't know how large the table is. Note the ridiculously small
> cost estimates in EXPLAIN ...

I see, I never knew about having to VACUUM/ANALYZE first. Thanks.

--
dave

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Mike Nolan 2004-03-29 04:45:24 Re: PG vs MySQL
Previous Message Mike Nolan 2004-03-29 04:37:41 Re: PG vs MySQL