Re: AW: AW: BUG #17923: Excessive warnings of collation version mismatch in logs

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Hans Buschmann <buschmann(at)nidsa(dot)net>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: AW: AW: BUG #17923: Excessive warnings of collation version mismatch in logs
Date: 2023-05-23 16:18:55
Message-ID: e55f8420-29f3-3c98-ba89-becbab6598b2@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 22.05.23 09:11, Hans Buschmann wrote:
> But I wonder, why this test is necessary at every autovacuum call at all?
>
> Woudn't it be sufficient to test it at server start time only once?

The main server process (postmaster) cannot access the database
contents. So we can only do it when we start a session process.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2023-05-23 20:50:35 BUG #17940: PostgreSQL Installer For Windows Cannot Initialize Cluster When BeyondTrust Installed
Previous Message Tom Lane 2023-05-23 14:07:12 Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN