| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function |
| Date: | 2012-03-23 14:55:52 |
| Message-ID: | 12822.1332514552@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas <rhaas(at)postgresql(dot)org> writes:
> Add notion of a "transform function" that can simplify function calls.
Why exactly was this thought to be a good idea:
> * A NULL original expression disables use of transform functions while
> * retaining all other behaviors.
AFAICT that buys nothing except to greatly complicate the API
specification for simplify_function, something that is now proving
problematic for Marti's requested refactoring [1]. If it's
inappropriate for a transform function to modify a CoerceViaIO call,
surely the transform function can be expected to know that.
regards, tom lane
[1] http://archives.postgresql.org/pgsql-hackers/2012-03/msg00694.php
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-03-23 15:25:58 | Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function |
| Previous Message | Robert Haas | 2012-03-23 12:51:12 | Re: [COMMITTERS] pgsql: Update docs on numeric storage requirements. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-03-23 15:02:18 | Re: heap_freeze_tuple locking requirements |
| Previous Message | David Fetter | 2012-03-23 14:53:19 | Re: Uppercase tab completion keywords in psql? |