El día lunes, marzo 24, 2025 a las 07:27:21a. m. +0100, Laurenz Albe escribió:
> On Mon, 2025-03-24 at 06:57 +0100, Matthias Apitz wrote:
> > El día lunes, febrero 24, 2025 a las 12:41:05p. m. +0100, Laurenz Albe
> > escribió:
> > > Perhaps I need not say that, but ALTER COLLATION ... REFRESH VER
On Fri, 2025-03-28 at 07:37 +0100, Matthias Apitz wrote:
> Anyway, does it make sense to ALTER COLLATION in these databases as well?
> >
> > I would say so, yes. At least on the template you are using for new
> > databases.
>
> $ psql -Upostgres template0
> Passwort für Benutzer postgres:
> psq
On Mon, 2025-03-24 at 06:57 +0100, Matthias Apitz wrote:
> El día lunes, febrero 24, 2025 a las 12:41:05p. m. +0100, Laurenz Albe
> escribió:
> > Perhaps I need not say that, but ALTER COLLATION ... REFRESH VERSION only
> > makes the warning disappear.
> >
> > If you want to avoid data corruption
El día lunes, febrero 24, 2025 a las 12:41:05p. m. +0100, Laurenz Albe escribió:
> Perhaps I need not say that, but ALTER COLLATION ... REFRESH VERSION only
> makes the warning disappear.
>
> If you want to avoid data corruption, rebuild all indexes on strings,
> then make the warning disappear.
Matthias Apitz wrote:
> Thanks. I did \l before which gives:
>
> List of databases
>Name| Owner | Encoding | Collate |Ctype| ICU Locale
> | Locale Provider | Access privileges
> +--+--+--
On Mon, 2025-02-24 at 13:07 +0100, Matthias Apitz wrote:
> Thanks. I did \l before which gives:
>
> List of databases
> Name | Owner | Encoding | Collate | Ctype | ICU Locale |
> Locale Provider | Access privileges
>
On Mon, Feb 24, 2025 at 6:53 AM Matthias Apitz
wrote:
[snip]
> pgsql -Usisis sisis
>
> sisis=# REINDEX (VERBOSE) DATABASE sisis;
> sisis=# ALTER COLLATION "de_DE.utf8" REFRESH VERSION;
> ALTER COLLATION
>
> Correct?
>
>
Just reindex those with text columns.
create or replace view dba.all_indices
Thanks. I did \l before which gives:
List of databases
Name| Owner | Encoding | Collate |Ctype| ICU Locale
| Locale Provider | Access privileges
+--+--+-+-++--
On Mon, Feb 24, 2025 at 12:33 PM Matthias Apitz
wrote:
> Thanks for your hint, Jeremy. But this does not work either:
>
> postgres=# SELECT collname, collversion FROM pg_collation where collname =
> 'de_DE.utf8';
> collname | collversion
> +-
> de_DE.utf8 | 2.38
> (1 r
On Mon, 2025-02-24 at 12:53 +0100, Matthias Apitz wrote:
> If I understand the other reply from Laurenz Albe right, the correct
> procedure would be:
>
> pgsql -Usisis sisis
> sisis=# REINDEX (VERBOSE) DATABASE sisis;
> sisis=# ALTER COLLATION "de_DE.utf8" REFRESH VERSION;
> ALTER COLLATION
>
>
Thanks. I tried a lot of combinations. Based on the output of \l
List of databases
Name| Owner | Encoding | Collate |Ctype| ICU Locale
| Locale Provider | Access privileges
+--+--+-+-
On Mon, 2025-02-24 at 02:32 -0800, Jeremy Schneider wrote:
> On Mon, 24 Feb 2025 11:08:43 +0100
> Matthias Apitz wrote:
> > What is the procedure on 13.1 to bring the external (glibc) version
> > in sync with. the used version in the PostgreSQL database?
>
> If I recall correctly, between version
Thanks for your hint, Jeremy. But this does not work either:
postgres=# SELECT collname, collversion FROM pg_collation where collname =
'de_DE.utf8';
collname | collversion
+-
de_DE.utf8 | 2.38
(1 row)
postgres=# ALTER COLLATION de_DE.utf8 REFRESH VERSION;
ERROR: sche
On Mon, 24 Feb 2025 11:08:43 +0100
Matthias Apitz wrote:
>
> What is the procedure on 13.1 to bring the external (glibc) version
> in sync with. the used version in the PostgreSQL database?
If I recall correctly, between versions 10 and 14 you need to use ALTER
COLLATION name REFRESH VERSION on
14 matches
Mail list logo
