From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Björn Lundin <b(dot)f(dot)lundin(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Order by and timestamp |
Date: | 2020-03-16 16:40:14 |
Message-ID: | 8265.1584376814@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
=?utf-8?Q?Bj=C3=B6rn_Lundin?= <b(dot)f(dot)lundin(at)gmail(dot)com> writes:
> Ooh - terrible sorry.
> The output from first post describing the database schema
> Was actually from my production machine - a raspberry pi.
> The pi hold a db on an usb-disk, which is pg_dump()ed every night and imported to ibm2 history db (the bad one)
> The schema is identical to the one with trouble - which is a history database
> Intended for testing
Hmmm ... schema is evidently the same, but locale seemingly not.
Is it possible this is a locale problem? I did not look closely
at the original data, but I'm suddenly wondering if it could be
explained by misinterpreting the date field order (month-day vs
day-month). Check the datestyle settings on both machines.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Samuel Smith | 2020-03-16 17:35:39 | Re: Invalid byte sequence errors on DB restore |
Previous Message | Björn Lundin | 2020-03-16 16:15:45 | Re: Order by and timestamp |