Re: Bogus collation version recording in recordMultipleDependencies

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Bogus collation version recording in recordMultipleDependencies
Date: 2021-04-19 18:13:37
Message-ID: CAH2-WzkCuqk+AXA=QuEcVBJEOhG7GLoymw=9fYsY5w=iGp6XjQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 18, 2021 at 4:23 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
> So IIUC the issue here is that the code could previously record useless
> collation version dependencies in somes cases, which could lead to false
> positive possible corruption messages (and of course additional bloat on
> pg_depend). False positive messages can't be avoided anyway, as a collation
> version update may not corrupt the actually indexed set of data, especially for
> glibc.

This argument seems completely absurd to me.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2021-04-19 18:16:55 Re: Windows default locale vs initdb
Previous Message Peter Geoghegan 2021-04-19 18:04:26 Re: Bogus collation version recording in recordMultipleDependencies