Re: WIP: Upper planner pathification

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: Upper planner pathification
Date: 2016-03-20 22:55:49
Message-ID: 56EF2A75.3000407@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/17/16 9:01 AM, Robert Haas wrote:
> I think that
> there are an awful lot of cases where extension authors haven't been
> able to quite do what they want to do without core changes because
> they couldn't get control in quite the right place; or they could do
> it but they had to cut-and-paste a lot of code.

FWIW, I've certainly run into this at least once, maybe twice. The case
I can think of offhand is doing function resolution with variant. I
don't remember the details anymore, but my recollection is that to get
what I needed I would have needed to copy huge swaths of the rewrite code.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2016-03-20 23:00:01 Re: multivariate statistics v14
Previous Message Thomas Munro 2016-03-20 22:52:43 Re: Performance degradation in commit ac1d794