Re: 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: BUG #17923: Excessive warnings of collation version mismatch in logs
Date: 2023-05-17 12:41:00
Message-ID: e87a8b12-7564-cd3a-f3c1-90e2005bb4e8@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 11.05.23 12:07, Hans Buschmann wrote:
> The problem is not at connection time (I only mentioned it for info).
>
>
> The problem is the endless repeating of these log entries without user
> login (cut a little bit at line end):
>
>
> 17:09:08 CEST  01000  1:> WARNING:  database "template1" has a collation
> version mismatch
> 17:09:08 CEST  01000  2:> DETAIL:  The database was created using
> collation version 2.36,
> 17:09:08 CEST  01000  3:> HINT:  Rebuild all objects in this database
> that use the defaul

I guess this is from the autovacuum background processes. Maybe we
should disable the warnings for those?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Joe Conway 2023-05-17 13:27:03 Re: BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM
Previous Message PG Bug reporting form 2023-05-17 09:42:26 BUG #17937: Corrupt Indexes after reusing DRBD Device on new VM