| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: Notice about costly ri checks |
| Date: | 2004-03-03 15:26:48 |
| Message-ID: | Pine.LNX.4.58.0403031624570.28778@sablons.cri.ensmp.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
> > This patch adds a "notice" at constraint creation time if the referential
> > integrity check is to be "costly", that is the comparison operator
> > involves some coercion.
>
> This is not the correct test at all.
You mean my morning 5mn programming will not be enough? ;-)
> The correct test would involve
> looking in pg_amop to see if the selected operator is a member of the
> opclass for the referenced column's index. (IIRC there are helper
> functions in lsyscache.c that will make this easier.)
Ok, I'll have a look.
--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2004-03-03 17:34:44 | notice about costly ri checks (2) |
| Previous Message | Tom Lane | 2004-03-03 14:58:39 | Re: Notice about costly ri checks |