From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: Should contrib modules install .h files? |
Date: | 2018-07-23 04:39:40 |
Message-ID: | 20180723043940.dc4s2qv6lefllg2d@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2018-Jul-23, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > On Sun, Jul 22, 2018 at 09:42:08PM -0400, Stephen Frost wrote:
> >> So, +1 from me for having a directory for each extension.
>
> > So, like Stephen, that's a +1 from me.
>
> Same here. One-file-per-extension is too strongly biased to tiny
> extensions (like most of our contrib examples).
>
> I don't have a real strong opinion on whether it's too late to
> push this into v11. I do not think it'd break anything other than
> packagers' lists of files to be installed ... but it does seem
> like a new feature, and we're past feature freeze.
Frankly, I'd rather make things as easy as possible for third-party
extension writers. I'd go as far as backpatching further (considering
transforms were introduced in 9.5) but I hesitate on that, because of
the packagers argument. pg11 seems fair game to me, though.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-07-23 04:56:56 | Re: Possible performance regression in version 10.1 with pgbench read-write tests. |
Previous Message | Andres Freund | 2018-07-23 04:24:27 | Re: wrong query result with jit_above_cost= 0 |