| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, John Naylor <jcnaylor(at)gmail(dot)com> |
| Subject: | Re: Mop-up for the bootstrap data conversion patch |
| Date: | 2018-04-07 12:25:44 |
| Message-ID: | 20180407122544.mpn66rtpn7m3p4yo@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I've always felt that the pg_foo_fn.h business was a kluge, and would
> be happy to get rid of it. But one could also argue that it would be
> a good design, if we adopted it uniformly instead of haphazardly.
> But that'd require more code churn, and there's no longer a lot to be
> gained thereby.
I vote for removing pg_foo_fn.h.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2018-04-07 12:27:15 | Re: WIP: Covering + unique indexes. (the good and the bad) |
| Previous Message | Alvaro Herrera | 2018-04-07 12:23:49 | Re: [HACKERS] Runtime Partition Pruning |