| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, Thom Brown <thom(at)linux(dot)com>, Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, "pgsql-hackers(at)postgreSQL(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |
| Date: | 2015-05-11 03:07:45 |
| Message-ID: | 20150511030745.GN12950@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-05-10 22:51:33 -0400, Robert Haas wrote:
> > And there's definitely some things
> > around that pretty much only still exist because changing them would
> > break too much stuff.
>
> Such as what?
Without even thinking about it:
* linitial vs lfirst vs lnext. That thing still induces an impedance
mismatch when reading code for me, and I believe a good number of
other people.
* Two 'string buffer' APIs with essentially only minor differences.
* A whole bunch of libpq APIs. Admittedly that's a bit more exposed than
lots of backend only things.
* The whole V0 calling convention that makes it so much easier to get
odd crashes.
Admittedly that's all I could come up without having to think. But I do
vaguely remember a lot of things we did not do because of bwcompat
concerns.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-11 03:15:33 | Re: feature freeze and beta schedule |
| Previous Message | Robert Haas | 2015-05-11 02:51:33 | Re: Custom/Foreign-Join-APIs (Re: [v9.5] Custom Plan API) |