| From: | Rod Taylor <rbt(at)rbt(dot)ca> |
|---|---|
| To: | Richard Huxton <dev(at)archonet(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, ow <oneway_111(at)yahoo(dot)com>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: 7.4 - FK constraint performance |
| Date: | 2004-02-13 13:57:20 |
| Message-ID: | 1076680640.10896.15.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-sql |
> In this precise example, could you not:
> 1. Check index for value
> 2. If found, seq-scan
>
> Of course that's only going to be a sensible thing to do if you're expecting
> one of two results:
> 1. Value not there
> 2. Lengthy seq-scan if it is there
Most of the queries are going to be for the other values (in which case
you've wasted an index scan) which is minor, but in the event there is a
single 239 you're still taking a big hit.
That is an awful lot of work to handle the non-existant case only.
--
Rod Taylor <rbt [at] rbt [dot] ca>
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
PGP Key: http://www.rbt.ca/rbtpub.asc
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2004-02-13 13:57:50 | Re: 7.4 - FK constraint performance |
| Previous Message | Zeugswetter Andreas SB SD | 2004-02-13 13:36:50 | Re: Transaction aborts on syntax error. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rod Taylor | 2004-02-13 13:57:50 | Re: 7.4 - FK constraint performance |
| Previous Message | Tomasz Myrta | 2004-02-13 13:34:54 | column alias and group by/having/order |