Skip site navigation (1)
Skip section navigation (2)
## Re: [COMMITTERS] pgsql: Add notion of a "transform function" thatcan simplify function

### In response to

### Responses

### pgsql-hackers by date

### pgsql-committers by date

On Fri, Mar 23, 2012 at 10:55:52AM -0400, Tom Lane wrote: > 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. We last spoke of that idea here, albeit in minimal detail: http://archives.postgresql.org/pgsql-hackers/2011-06/msg00918.php > 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. I did it that way because it looked wrong to pass the same CoerceViaIO node to transforms of both the input and output functions. Thinking about it again now, doing so imposes no fundamental problems. Feel welcome to change it.

- Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function at 2012-03-23 14:55:52 from Tom Lane

- Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function at 2012-03-23 15:36:49 from Tom Lane

Next: From:Tom LaneDate:2012-03-23 15:31:54Subject: Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify functionPrevious: From: Billy EarneyDate: 2012-03-23 15:28:48Subject: query cache

Next: From:Tom LaneDate:2012-03-23 15:31:54Subject: Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify functionPrevious: From: Robert HaasDate: 2012-03-23 15:25:58Subject: Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function