Re: Should we rename amapi.h and amapi.c?

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Ashwin Agrawal <aagrawal(at)pivotal(dot)io>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Should we rename amapi.h and amapi.c?
Date: 2019-12-24 13:22:22
Message-ID: alpine.DEB.2.21.1912241418080.3339@pseudo
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Bonjour Michaël,

> the syscache mainly, so instead the attached patch does the following
> changes:
> - amapi.h -> indexam.h
> - amapi.c -> indexamapi.c. Here we have an equivalent in access/table/
> as tableamapi.c.
> - amvalidate.c -> indexamvalidate.c
> - amvalidate.h -> indexamvalidate.h
> - genam.c -> indexgenam.c
>

Patch applies cleanly, compiles, make check-world ok.

The change does not attempt to keep included files in ab order. Should it
do that, or is it fixed later by some reindentation phase?

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-12-24 15:15:20 weird libpq GSSAPI comment
Previous Message Anastasia Lubennikova 2019-12-24 12:29:23 Re: Building infrastructure for B-Tree deduplication that recognizes when opclass equality is also equivalence