| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_statistic_ext.staenabled might not be the best column name |
| Date: | 2017-04-13 16:31:26 |
| Message-ID: | 20170413163126.lqlzvjlezhdb7zcc@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2017-04-13 16:37:33 | Re: Letting the client choose the protocol to use during a SASL exchange |
| Previous Message | Peter Eisentraut | 2017-04-13 16:28:25 | Re: tablesync patch broke the assumption that logical rep depends on? |