| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Subject: | Re: Add parallelism and glibc dependent only options to reindexdb |
| Date: | 2019-07-01 21:46:48 |
| Message-ID: | 20190701214648.GA9427@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Jul-02, Thomas Munro wrote:
> On Tue, Jul 2, 2019 at 8:34 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> > Even if that's just me being delusional, I'd still prefer Alvaro's
> > approach to have distinct switches for each collation system.
>
> Hi Julien,
>
> Makes sense. But why use the name "glibc" in the code and user
> interface? The name of the collation provider in PostgreSQL is "libc"
> (for example in the CREATE COLLATION command), and the problem applies
> no matter who makes your libc.
Makes sense. "If your libc is glibc and you go across an upgrade over
version X, please use --include-rule=libc-collation"
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2019-07-01 22:38:30 | Re: range_agg |
| Previous Message | Thomas Munro | 2019-07-01 21:40:25 | Re: Add parallelism and glibc dependent only options to reindexdb |