| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Nathan Boley <npboley(at)gmail(dot)com> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Collect frequency statistics for arrays |
| Date: | 2012-03-01 22:19:22 |
| Message-ID: | 18867.1330640362@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Nathan Boley <npboley(at)gmail(dot)com> writes:
> Maybe this is bad design, but I've gotten in the habit of storing
> sequences as arrays and I commonly join on them. I looked through my
> code this morning, and I only have one 'range' query ( of the form
> described up-thread ), but there are tons of the form
> SELECT att1, attb2 FROM rela, relb where rela.seq_array_1 = relb.seq_array;
What do you mean by "storing sequences as arrays"? Can you demonstrate
that the existing stats are relevant at all to the query you're worried
about?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2012-03-01 22:34:48 | Re: Caching for stable expressions with constant arguments v6 |
| Previous Message | Nathan Boley | 2012-03-01 22:16:53 | Re: Collect frequency statistics for arrays |