| From: | ow <oneway_111(at)yahoo(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: FK Constraints, indexes and performance |
| Date: | 2003-10-07 00:37:33 |
| Message-ID: | 20031007003733.26679.qmail@web21401.mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> It looks to me like the 7.3 planner will not choose indexscans for the FK
> check queries in this example, because the comparison operators are
> misconstrued as shown in this thread:
> http://archives.postgresql.org/pgsql-hackers/2003-03/msg00997.php
> The equality operator on your domain is taken to be "oideq" which won't
> be the same operator associated with the index on the column.
>
> This seems to be fixed in 7.4. In 7.3 I'd counsel not introducing
> domains unnecessarily.
>
> regards, tom lane
It looks like it worked. I moved to 7.4.b4 and, in my case, performance
improvement on insert is drastic (about 30x). Thanks
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | sad | 2003-10-07 07:07:45 | privileges |
| Previous Message | Bruno Wolff III | 2003-10-06 16:56:09 | Re: create new field |