From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Andrus <kobruleht2(at)hot(dot)ee>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Query returns no rows in pg_basebackup cluster |
Date: | 2020-05-21 22:13:27 |
Message-ID: | ea1e505d-d049-1d1d-e3b3-e655928949b8@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/21/20 1:20 PM, Andrus wrote:
> Hi!
>
> In windows pg_basebackup was used to create base backup from Linux server.
> baas column data type is character(8)
>
> In Linux server query
> select * from firma1.desktop where baas='_LOGIFAI'
>
> returns 16 rows.
>
> Windows server this query returns 0 rows.
>
> In Windows server same query using like
>
> select * from firma1.desktop where baas like '_LOGIFAI'
>
> returns properly 16 rows.
Are you referring to two different instances of Postgres on Windows?
> Maybe this is because database locale is not known in windows:
>
> CREATE DATABASE sba
> WITH OWNER = sba_owner
> ENCODING = 'UTF8'
> LC_COLLATE = 'et_EE.UTF-8'
> LC_CTYPE = 'et_EE.UTF-8'
> TABLESPACE = pg_default
> CONNECTION LIMIT = -1;
>
> Correct encoding for windows should be
>
> LC_COLLATE = 'Estonian_Estonia.1257'
> LC_CTYPE = 'Estonian_Estonia.1257'
>
> IF so how to to fix windows cluster so that query returns proper result
> in windows also?
> Database in Windows is in read-only (recovery) mode so it cannot changed.
> Postgres 12 is used.
>
> Andrus.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-05-21 22:47:25 | Re: Query returns no rows in pg_basebackup cluster |
Previous Message | Adrian Klaver | 2020-05-21 22:05:24 | Re: Table partitioning for cloud service? |