| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | reijo(dot)suhonen(at)valtori(dot)fi |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16404: PostgreSQL 12.2: Database restore does not accept the EEST time zone. |
| Date: | 2020-04-30 14:08:44 |
| Message-ID: | 21109.1588255724@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-04-30 14:15:51 | Back-patch is necessary? Re: Don't try fetching future segment of a TLI. |
| Previous Message | Tom Lane | 2020-04-30 13:57:46 | Re: BUG #16403: set_bit function does not have expected effect |