| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Thomas Hallgren <thomas(at)tada(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Question about casts |
| Date: | 2006-05-18 20:16:56 |
| Message-ID: | 20448.1147983416@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> Every cast costs space and lookup time.
Actually, we could probably have a net time savings here if the text
cast cases were hard-wired into parse_coerce.c. The reason is that
about 10% of the default entries in pg_cast are "retail" implementations
of text-to-or-from-foo casts, and we could get rid of all those entries,
not to mention the associated pg_proc entries and underlying code.
That would certainly cut search time in pg_cast enough to pay for a
couple of hard-wired "typoid == TEXTOID" checks.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philippe Schmid | 2006-05-18 20:17:32 | Re: [OT] MySQL is bad, but THIS bad? |
| Previous Message | Lukas Smith | 2006-05-18 19:58:21 | Re: [OT] MySQL is bad, but THIS bad? |