| From: | Marcin Stępnicki <mstepnicki(at)gmail(dot)com> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: DISTINCT ON not working...? |
| Date: | 2007-02-20 12:33:55 |
| Message-ID: | pan.2007.02.20.12.33.55.976823@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Dnia Tue, 20 Feb 2007 15:36:32 +1100, Phillip Smith napisał(a):
> Removing the CASE statement all together:
> SELECT DISTINCT ON (ean)
> ean,
> count(*)
> FROM TMPTABLE
> WHERE code NOT IN (SELECT code FROM stock_deleted)
> AND ean IS NOT NULL
> GROUP BY ean
>
> Still gives me:
> 3246576919422 2
Wild guess - have you tried reindexing this table? I haven't seen
corrupted indexes since 7.1, though - it usually means subtle hardware
problems.
--
| And Do What You Will be the challenge | http://apcoln.linuxpl.org
| So be it in love that harms none | http://biznes.linux.pl
| For this is the only commandment. | http://www.juanperon.info
`---* JID: Aragorn_Vime(at)jabber(dot)org *---' http://www.naszedzieci.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2007-02-20 14:26:01 | Re: can someone explain confusing array indexing nomenclature |
| Previous Message | Achilleas Mantzios | 2007-02-20 07:42:17 | Re: can someone explain confusing array indexing nomenclature |