Re: Query returns no rows in pg_basebackup cluster
От | Adrian Klaver |
---|---|
Тема | Re: Query returns no rows in pg_basebackup cluster |
Дата | |
Msg-id | ea1e505d-d049-1d1d-e3b3-e655928949b8@aklaver.com обсуждение исходный текст |
Ответ на | Query returns no rows in pg_basebackup cluster ("Andrus" <kobruleht2@hot.ee>) |
Ответы |
Re: Query returns no rows in pg_basebackup cluster
Re: Query returns no rows in pg_basebackup cluster |
Список | 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.klaver@aklaver.com
В списке pgsql-general по дате отправления: