Andrew Sullivan <ajs at crankycanuck.ca> writes:
> That said, this makes my teeth hurt just to suggest it.  But the log
> shipping today doesn't really do what you want.  I know there was some
> intended work to allow filtering in 2.x.  I don't know if it got off
> the ground.  Chris?

Jan's looking at implementing an admin tool to be rather friendlier
than what we have now; the notion of doing filtering seems to be a
good couple of steps further down the road.

That's smelling like "3.x", at this point.  We have loosely talked
about having "smarter triggers" that store more of the metadata in
more intelligent form, so that you could indeed pick and choose and
even transform on the way through.

It has gotten steps further, conceptually; Jan, Simon and I had a chat
at PGCon about a "wildly more intelligent COPY" that would get us the
kinds of efficiencies that COPY does for I/U/D updates.  A key thing
about that would be making it generally useful as a "Data Load Tool"
(e.g. - presumably with the potential to be popular for data
warehouse-like applications) so that it wouldn't hang as a
Slony-I-only "bag on the side."  But implementation hasn't started,
and *that* would be a logical prerequisite to filtering.
-- 
"cbbrowne","@","cbbrowne.com"
http://linuxdatabases.info/info/nonrdbms.html
Rules of  the Evil Overlord  #228.  "If the  hero claims he  wishes to
confess  in public  or to  me  personally, I  will remind  him that  a
notarized deposition will serve just as well."
<http://www.eviloverlord.com/>