From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: slotname vs slot_name |
Date: | 2014-06-05 11:18:19 |
Message-ID: | 20140605111819.GJ2789@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2014-06-05 14:12:31 +0300, Heikki Linnakangas wrote:
> On 06/05/2014 01:57 PM, Andres Freund wrote:
> >On 2014-06-05 10:57:58 +0900, Fujii Masao wrote:
> >We have:
> >* pg_ldecoding (Heikki)
> >* pg_lcse or pg_lcset (Petr)
> >* pg_logical (Andres)
> >
> >I like, what a surprise, my own suggestion best. The name seems more
> >versatile because it's not restricted to decoding.
>
> The problem with pg_logical is that it's not restricted to much at all ;-),
> "logical" is an awfully generic name.
So is base/, global/, pg_stat/,... I don't think we need
uber-descriptive names here. I do think it's descriptive enough that
unrelated data won't be looked for in there. And imo that's the case.
> BTW, the stuff that we have in pg_llog are not really logs at all, so
> pg_llog was always a misnomer.
I'm not fighting for it :).
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Linos | 2014-06-05 11:32:27 | performance regression in 9.2/9.3 |
Previous Message | Heikki Linnakangas | 2014-06-05 11:13:58 | Re: slotname vs slot_name |