From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: collations in shared catalogs? |
Date: | 2015-02-25 18:40:24 |
Message-ID: | 20150225184024.GS5169@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Tom Lane wrote:
> >> Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> >>> How did that happen? And how could it possibly work?
>
> >> It probably doesn't, and the reason nobody has noticed is that the
> >> security label stuff has fewer users than I have fingers (and those
> >> people aren't using provider names that would cause anything interesting
> >> to happen).
>
> > The BDR code has recently started using security labels as a place to
> > store table-specific data. That widens its use a fair bit ... and most
> > likely, other extensions will also start using them as soon as they
> > realize that it can be used for stuff other than actual security labels.
>
> Yeah? Would they be OK with redefining the provider field as "name",
> or would the length limit be an issue?
Nah, it's fine. The provider name used there is "bdr".
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2015-02-25 19:39:08 | Re: Performance improvement for joins where outer side is unique |
Previous Message | Tom Lane | 2015-02-25 18:21:05 | Re: collations in shared catalogs? |