| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | André Volpato <andre(dot)volpato(at)ecomtecnologia(dot)com(dot)br> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Postgres not using array |
| Date: | 2008-08-21 14:28:00 |
| Message-ID: | 23465.1219328880@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
=?ISO-8859-1?Q?Andr=E9_Volpato?= <andre(dot)volpato(at)ecomtecnologia(dot)com(dot)br> writes:
> Explain output:
> HashAggregate (cost=19826.23..19826.96 rows=73 width=160) (actual
> time=11826.754..11826.754 rows=0 loops=1)
> -> Subquery Scan b2 (cost=19167.71..19817.21 rows=722 width=160)
> (actual time=11826.752..11826.752 rows=0 loops=1)
> Filter: (bds_internacoes(200805, 200806, (b2.cod)::text,
> 'qtdI'::text, 'P'::bpchar) >= 1::numeric)
> -> Limit (cost=19167.71..19248.89 rows=2165 width=48) (actual
> time=415.157..621.043 rows=28923 loops=1)
So I guess the question is "what is the bds_internacoes function, and
why is it so slow?"
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2008-08-21 14:39:24 | Re: Slow query with a lot of data |
| Previous Message | Mark Mielke | 2008-08-21 14:16:40 | Re: Postgres not using array |