Re: Allowing extensions to supply operator-/function-specific info

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Paul Ramsey <pramsey@cleverelephant.ca>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2019-03-04T21:13:41Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Allow extensions to generate lossy index conditions.
- 74dfe58a5927 12.0 landed
Build out the planner support function infrastructure.
- a391ff3c3d41 12.0 landed
Create the infrastructure for planner support functions.
- 1fb57af92069 12.0 landed
Disable transforms that replaced AT TIME ZONE with RelabelType.
- c22ecc6562aa 10.0 cited

Paul Ramsey <pramsey@cleverelephant.ca> writes:
> I had what seemed to be working code except for a couple rare cases,
> but when I fixed those cases it turned out that I had a major problem:
> building a <var> OP <const> expression works fine, but building a
> <const> OP <var> expression returns me an error.

Yup, you're not supposed to do that.  The output expression *must* have
the index key on the left, it's up to you to commute the operator if
needed to make that happen.

			regards, tom lane