Re: BUG #16561: timestamp with time zone microseconds inconsistently recorded correctly and incorrectly

From: Peter Thomas <peter(dot)thomas(at)mccarthy(dot)co(dot)nz>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16561: timestamp with time zone microseconds inconsistently recorded correctly and incorrectly
Date: 2020-07-30 02:05:07
Message-ID: 1451602440.227759.1596074707411.JavaMail.zimbra@mccarthy.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Thomas,

pg_controldata -D pgdata

returns

Date/time type storage: 64-bit integers

Regarding the parallel execution on two same-server databases, I can also reproduce the problem running sequentially (same-thread) across the two same-server databases.

(Note: in both parallel and sequential execution the multi-db same-query inserts are both completed before the multi-db same-query updates get executed)

What is interesting is that in either threading case the incorrect timestamp values are written consistently in both databases, which is a down-vote for random corruption.

Regards,

Peter Thomas

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Thomas 2020-07-30 02:44:13 Re: BUG #16561: timestamp with time zone microseconds inconsistently recorded correctly and incorrectly
Previous Message Thomas Munro 2020-07-30 01:39:57 Re: BUG #16561: timestamp with time zone microseconds inconsistently recorded correctly and incorrectly