Re: pg_statistic_ext.staenabled might not be the best column name
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>,
Alvaro Herrera <alvherre@2ndquadrant.com>
Date: 2017-04-13T12:28:06Z
Lists: pgsql-hackers
Tomas Vondra <tomas.vondra@2ndquadrant.com> writes: > On 04/12/2017 03:36 PM, David Rowley wrote: >> "stakind" seems like a better name. I'd have personally gone with >> "statype" but pg_statistic already thinks stakind is better. > +1 to stakind I agree with that, but as long as we're rethinking column names here, was it a good idea to use the same "sta" prefix in pg_statistic_ext as in pg_statistic? I do not think there's anyplace else where we're using the same table-identifying prefix in two different catalogs, and it seems a little pointless to follow that convention at all if we're not going to make it a unique prefix. We could go with "ste" perhaps, or break the convention of 3-character prefixes and go with "stae". regards, tom lane
Commits
-
Rename columns in new pg_statistic_ext catalog
- ee6922112e9b 10.0 landed