Re: could not determine encoding for locale "et_EE.UTF-8": codeset is "CPUTF-8" in pg_restore

Hi!

>There seems to a difference of opinion of what Baltic Code Page to use:
>https://en.wikipedia.org/wiki/Code_page_775
>https://en.wikipedia.org/wiki/Windows-1257
>The post below shows a users method of dealing with this for another CP:
>https://www.postgresql.org/message-id/549275CC.4010607%40gmail.com

Console code page 775 message appears since psql is console application 
running from command line.

It does not have any relation to pg_dump/pg_restore issue since console code 
page is not used in this case.

There is Estonian locale everywhere.
Maybe this warning is harmless since Linux code page is ignored and default 
collation is used.
All table definitions in restored database contain references to default 
collation:

CREATE TABLE firma1.acquirpo
(
    kassanr numeric(3,0) NOT NULL,
    policyid character(2) COLLATE pg_catalog."default" NOT NULL,
    trantype character(6) COLLATE pg_catalog."default",
    tacdefault character(10) COLLATE pg_catalog."default",
    tacdenial character(10) COLLATE pg_catalog."default",
    taconline character(10) COLLATE pg_catalog."default",
    floorlimit numeric(12,0),
    randselthr numeric(12,0),
    minrandper numeric(2,0),
    maxrandper numeric(2,0),
    CONSTRAINT acquirpo_pkey PRIMARY KEY (kassanr, policyid)
)

TABLESPACE pg_default;

Same warning appears two times. This command execute by pg_restore probably 
causes this (harmless?)  warning:

CREATE DATABASE mydb
    WITH
    OWNER = mydb_owner
    ENCODING = 'UTF8'
    LC_COLLATE = 'et_EE.UTF-8'
    LC_CTYPE = 'et_EE.UTF-8'
    TABLESPACE = pg_default
    CONNECTION LIMIT = -1;

If new database is created manually in windows cluster the following command 
is generated:


CREATE DATABASE mydbmanually
    WITH
    OWNER = mydbmanually_owner
    ENCODING = 'UTF8'
    LC_COLLATE = 'Estonian_Estonia.1257'
    LC_CTYPE = 'Estonian_Estonia.1257'
    TABLESPACE = pg_default
    CONNECTION LIMIT = -1;

Andrus.