From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Rename files and headers related to index AM |
Date: | 2019-12-26 18:14:51 |
Message-ID: | 20191226181451.czc4zad3k5qhjoni@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Hi,
On 2019-12-26 11:46:06 -0300, Alvaro Herrera wrote:
> On 2019-Dec-25, Michael Paquier wrote:
>
> > Rename files and headers related to index AM
> >
> > The following renaming is done so as source files related to index
> > access methods are more consistent with table access methods (the
> > original names used for index AMs ware too generic, and could be
> > confused as including features related to table AMs):
> > - amapi.h -> indexam.h.
> > - amapi.c -> indexamapi.c. Here we have an equivalent with
> > backend/access/table/tableamapi.c.
> > - amvalidate.c -> indexamvalidate.c.
> > - amvalidate.h -> indexamvalidate.h.
> > - genam.c -> indexgenam.c.
> > - genam.h -> indexgenam.h.
>
> I think this commit was too hasty. There's too many people distracted
> by holidays.
+1
> I suppose that this renaming is going to impact all third-party
> extensions that use those headers. If there are no complaints to this,
> that means we can do some more invasive header refactoring, unimpeded by
> such complaints either.
Yea, this seems like a much bigger move than warranted. Especially
without a backward compat header put into place.
Imo this ought to be reverted.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2019-12-26 18:26:51 | Re: pgsql: Rename files and headers related to index AM |
Previous Message | Tom Lane | 2019-12-26 16:20:21 | pgsql: Improve comments in utils/rel.h. |