Horton

Re: [REVIEW] pg_last_xact_insert_timestamp

Kyotaro Horiguchi <horiguchi.kyotaro@oss.ntt.co.jp>

View thread
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@oss.ntt.co.jp>
To: masao.fujii@gmail.com
Cc: pgsql-hackers@postgresql.org
Date: 2011-09-30T02:24:43Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Treat 2PC commit/abort the same as regular xacts in recovery.

Hello,

I understand that it has been at least practically no problem.

Ok, I send this patch to comitters.

Thanks for your dealing with nuisance questions.


At Thu, 29 Sep 2011 21:21:32 +0900, Fujii Masao <masao.fujii@gmail.com> wrote in <CAHGQGwG0C21F0CZY5ExX-49dxdx7hJuNeiBBJ0Tzvh+7vMXWgw@mail.gmail.com>
> >> > Nevertheless this is ok for all OSs, I don't know whether
> >> > initializing TimestampTz(double, int64 is ok) field with 8 bytes
...
> I believe it's safe. Such a code is placed elsewhere in the source, too.
> If it's unsafe, we should have received lots of bug reports related
> to that. But we've not.

Regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center