Re: [HACKERS] pg_statistic_ext.staenabled might not be the best column name

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] pg_statistic_ext.staenabled might not be the best column name
Дата
Msg-id 11427.1492086486@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] pg_statistic_ext.staenabled might not be the best column name  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Ответы Re: [HACKERS] pg_statistic_ext.staenabled might not be the bestcolumn name
Список 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



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Masahiko Sawada
Дата:
Сообщение: Re: [HACKERS] Quorum commit for multiple synchronous replication.
Следующее
От: Yorick Peterse
Дата:
Сообщение: Re: [HACKERS] [PATCH] Document the order of changing certain settingswhen using hot-standby servers