From: Tom Lane <tgl@sss.pgh.pa.us>
To: reijo.suhonen@valtori.fi
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16404: PostgreSQL 12.2: Database restore does not accept the
 EEST time zone.
In-reply-to: <16404-4603a99603fbd04c@postgresql.org>
References: <16404-4603a99603fbd04c@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 30 Apr 2020 08:05:05 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <21108.1588255724.1@sss.pgh.pa.us>
Date: Thu, 30 Apr 2020 10:08:44 -0400
Message-ID: <21109.1588255724@sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> Database restore does not accept the EEST time zone. PostgreSQL version 10
> restore accept EEST timezone.

Works for me:

# select '2020-04-30 10:01:32.277852 EEST'::timestamptz;
          timestamptz          
-------------------------------
 2020-04-30 03:01:32.277852-04
(1 row)

Maybe you are using a non-default timezone_abbreviations file? [1]

In any case, it's not very clear why this would be a database
restore issue.  Dump/restore should always use numeric UTC
offsets in dumped timestamps.

Anyway, you'll need to provide a lot more detail if you want
help on this.

			regards, tom lane

[1] https://www.postgresql.org/docs/current/datetime-config-files.html