Re: tracking commit timestamps

On Fri, Dec 19, 2014 at 3:53 PM, Noah Misch <noah@leadboat.com> wrote:
> localhost template1=# select clock_timestamp(), pg_sleep(.1 * (n % 2)) from generate_series(0,7) t(n);
>         clock_timestamp        | pg_sleep
> -------------------------------+----------
>  2014-12-18 08:34:34.522126+00 |
>  2014-12-18 08:34:34.522126+00 |
>  2014-12-18 08:34:34.631508+00 |
>  2014-12-18 08:34:34.631508+00 |
>  2014-12-18 08:34:34.74089+00  |
>  2014-12-18 08:34:34.74089+00  |
>  2014-12-18 08:34:34.850272+00 |
>  2014-12-18 08:34:34.850272+00 |
> (8 rows)
So, we would need additional information other than the node ID *and*
the timestamp to ensure proper transaction commit ordering on Windows.
That's not cool and makes this feature very limited on this platform.
-- 
Michael