Re: logical changeset generation v6.5 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: logical changeset generation v6.5
Date
Msg-id 20131105152141.GA14819@awork2.anarazel.de
Whole thread Raw
In response to logical changeset generation v6  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: logical changeset generation v6.5
Re: logical changeset generation v6.5
List pgsql-hackers
Hi,

Attached to this mail and in the xlog-decoding-rebasing-remapping branch
in my git[1] repository you can find the next version of the patchset that:
* Fixes full table rewrites of catalog tables using the method Robert
  prefers (which is to log rewrite mappings to disk)
* Extract the REPLICA IDENTITY as configured with ALTER TABLE for the
  old tuple for UPDATEs and DELETEs
* Much better support for synchronous replication
* Better resource cleanup (as in we need less local WAL available)
* Lots of smaller fixes

The change around REPLICA IDENTITY is *incompatible* to older output
plugins since we now log tuples using the table's TupleDesc, not the
indexes.

Robert, I'd be very grateful if you could have a look at patch 0007
implementing what we've discussed. I kept it separate to make it easier
to look at it in isolation, but I think in the end it partially should
be merged into the wal_level=logical patch.
I still think the "wide cmin/cmax" solution is more elegant and has
wider applicability, but this works as well although it's about 5 times
the code.

Comments?

[1]: http://git.postgresql.org/gitweb/?p=users/andresfreund/postgres.git;a=summary
Greetings,

Andres Freund

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

Attachment

pgsql-hackers by date:

Previous
From: Claudio Freire
Date:
Subject: Re: Fast insertion indexes: why no developments
Next
From: Leonardo Francalanci
Date:
Subject: Re: Fast insertion indexes: why no developments