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

In response to

• pgsql: Add notion of a "transform function" that can simplifyfunction at 2011-06-22 02:21:43 from Robert Haas

Responses

• Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function at 2012-03-23 15:25:58 from Robert Haas
• Re: [COMMITTERS] pgsql: Add notion of a "transform function" thatcan simplify function at 2012-03-23 15:31:47 from Noah Misch

pgsql-hackers by date

Next:	From: Alvaro Herrera	Date: 2012-03-23 15:02:18
	Subject: Re: heap_freeze_tuple locking requirements
Previous:	From: David Fetter	Date: 2012-03-23 14:53:19
	Subject: Re: Uppercase tab completion keywords in psql?

pgsql-committers by date

Next:	From: Robert Haas	Date: 2012-03-23 15:25:58
	Subject: Re: [COMMITTERS] pgsql: Add notion of a "transform function" that can simplify function
Previous:	From: Robert Haas	Date: 2012-03-23 12:51:12
	Subject: Re: [COMMITTERS] pgsql: Update docs on numeric storage requirements.