Re: tracking commit timestamps - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: tracking commit timestamps
Date
Msg-id CA+U5nM+uW4JzqdXL9S61C3hKV0z5ivHxDQoBvMasUbK0wJmwkw@mail.gmail.com
Whole thread Raw
In response to Re: tracking commit timestamps  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: tracking commit timestamps
List pgsql-hackers
On 14 November 2014 17:12, Robert Haas <robertmhaas@gmail.com> wrote:

> We are not talking about loading 20 new
> requirements on top of this patch; that would be intolerable.  We're
> talking about adding one additional piece of information that has been
> requested multiple times over the years.

The requested information is already available, as discussed. Logical
decoding adds commit ordering for *exactly* the purpose of using it
for replication, available to all solutions. This often requested
feature has now been added and doesn't need to be added twice.

So what we are discussing is adding a completely superfluous piece of
information.

Not including the LSN info does nothing to trigger based replication,
which will no doubt live on happily for many years. But adding LSN
will slow down logical replication, for no purpose at all.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Re: Segmentation fault in pg_dumpall from master down to 9.1 and other bug introduced by RLS
Next
From: Peter Geoghegan
Date:
Subject: Useless dead struct in parse_func.h