| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Oleg Bartunov'" <oleg(at)sai(dot)msu(dot)su>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Teodor Sigaev <teodor(at)stack(dot)net> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | AW: handling NULLS in GiST |
| Date: | 2001-07-16 14:43:10 |
| Message-ID: | 11C1E6749A55D411A9670001FA687963368388@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> we noticed you changed gist.c to handle NULLS. It seems there is
> problem with your changes.
....
> I remind we have choosen to leave NULLs because vacuum complained about
> different number of tuples in heap and index and all our opclasses work
> correctly with NULLs. Did you change vacuum code so it will not complain ?
If the opclasses handle NULLs, then they should be in the index.
Leaving them out would imho be better handled with the partial index code.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2001-07-16 14:46:49 | Re: Planned changes to pg_am catalog |
| Previous Message | Oleg Bartunov | 2001-07-16 14:06:44 | handling NULLS in GiST |