| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> |
| Cc: | "Teodor Sigaev" <teodor(at)sigaev(dot)ru>, "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Remove lossy-operator RECHECK flag? |
| Date: | 2008-04-11 19:02:44 |
| Message-ID: | 15100.1207940564@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com> writes:
> Just wanted to point out that I personnally use the capability to
> remove the RECHECK of PostGIS opclass (I define a similar opclass
> without the recheck) when I enforce the SRID in the application:
To be blunt, that seems like a really bad idea, and I have not the
slightest hesitation about breaking your ability to do it. How
do you know that the recheck-need corresponds to what you are testing
on the application side?
If there's actually some safe, consistent use for such behavior
then I think you need to lobby the PostGIS project to provide
access to it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2008-04-11 19:04:47 | Re: Commit fest queue |
| Previous Message | Decibel! | 2008-04-11 18:53:11 | Re: Separate psql commands from arguments |