Re: Add parallelism and glibc dependent only options to reindexdb

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: 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:40:25
Message-ID: CA+hUKGJK24Q0zOH4Z5X++jin6J5ZckLtpXksxE5Sj7F7A83LDA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Thomas Munro
https://enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-07-01 21:46:48 Re: Add parallelism and glibc dependent only options to reindexdb
Previous Message Peter Geoghegan 2019-07-01 21:21:40 Re: Add parallelism and glibc dependent only options to reindexdb