From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
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-02 08:16:22 |
Message-ID: | CAOBaU_YAZdCzJCdTrJOWHfe_Zh2_mMr8Hiu05XXxrPYg=A9hEA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 1, 2019 at 11:21 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>
> On Mon, Jul 1, 2019 at 1:34 PM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> > I have a vague recollection that ICU was providing some backward
> > compatibility so that even if you upgrade your lib you can still get
> > the sort order that was active when you built your indexes, though
> > maybe for a limited number of versions.
>
> That isn't built in. Another database system that uses ICU handles
> this by linking to multiple versions of ICU, each with its own UCA
> version and associated collations. I don't think that we want to go
> there, so it makes sense to make an upgrade that crosses ICU or glibc
> versions as painless as possible.
>
> Note that ICU does at least provide a standard way to use multiple
> versions at once; the symbol names have the ICU version baked in.
> You're actually calling the functions using the versioned symbol names
> without realizing it, because there is macro trickery involved.
Ah, thanks for the clarification!
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2019-07-02 08:22:29 | Re: Refactoring base64 encoding and decoding into a safer interface |
Previous Message | Prabhat Sahu | 2019-07-02 08:11:47 | Attached partition not considering altered column properties of root partition. |