| From: | Thomas Lockhart <lockhart(at)fourpalms(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | iscacheable for date/time? |
| Date: | 2001-09-26 13:08:48 |
| Message-ID: | 3BB1D360.477BF90A@fourpalms.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I'm looking at pg_proc.h to adjust the cacheable attribute for date/time
functions. Can anyone recall why the interval data type would have been
considered non-cacheable? I didn't make internal changes to that type,
but istm that it should be cacheable already.
For timestamp and timestamptz, I've eliminated the "current" special
value which afaicr is the only reason timestamp had not been cacheable
in the past. Are there any functions which should *not* be considered
cacheable for those types? Apparently the _in() and _out() functions
should not be? Everything else is deterministic so would seem to be a
candidate.
Comments?
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-09-26 13:17:21 | Re: iscacheable for date/time? |
| Previous Message | Reinoud van Leeuwen | 2001-09-26 12:53:14 | optimizer question |