Re: [HACKERS] pg_statistic_ext.staenabled might not be the bestcolumn name - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] pg_statistic_ext.staenabled might not be the bestcolumn name
Date
Msg-id 20170413163126.lqlzvjlezhdb7zcc@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] pg_statistic_ext.staenabled might not be the best column name  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] pg_statistic_ext.staenabled might not be the bestcolumn name  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
> > On 4/13/17 08:37, Heikki Linnakangas wrote:
> >> We have a bunch of > 3-character prefixes already: amop*, amproc*, 
> >> enum*, cast*. But I think I nevertheless like "ste" better.
> 
> > "stx" perhaps?
> 
> > I would also be in favor of changing it to something other than "sta".
> 
> "stx" sounds pretty good to me --- it seems like e.g. "stxkind" is
> more visibly distinct from "stakind" than "stekind" would be.
> 
> Any objections out there?

stx sounds good to me too.  I'll see about a patch this afternoon.

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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] tablesync patch broke the assumption that logical repdepends on?
Next
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] Letting the client choose the protocol to use during aSASL exchange