Re: Inconsistency between table am callback and table function names

On 2019-May-10, Andres Freund wrote:

> My personal opinion is that this is more churn than I think is useful to
> tackle after feature freeze, with not sufficient benefits.  If others
> chime in, voting to do this, I'm OK with doing that, but otherwise I
> think there's more important stuff to do.

One issue is that if we don't change things now, we can never change it
afterwards, so we should make some effort to ensure that naming is
sensible.  And we already changed the names of the whole interface.

I'm not voting to accept all of Ashwin's proposals right away, only to
have the names considered.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services