From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Exposing the Xact commit order to the user |
Date: | 2010-06-01 15:09:06 |
Message-ID: | 201006011509.o51F96U24923@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jan Wieck wrote:
> >> > I see no problem with integrating that into core, technically or
> >> > philosophically.
> >> >
> >>
> >> Which means that if I want to allow a consumer of that commit order data
> >> to go offline for three days or so to replicate the 5 requested, low
> >> volume tables, the origin needs to hang on to the entire WAL log from
> >> all 100 other high volume tables?
> >
> > I suggest writing an external tool that strips out what you need that
> > can be run at any time, rather than creating a new data format and
> > overhead for this usecase.
> >
>
> Stripping it out from what?
Stripping it from the WAL. Your system seems to require double-writes
on a commit, which is something we have avoided in the past.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-06-01 15:09:38 | Re: dividing money by money |
Previous Message | Jan Wieck | 2010-06-01 15:06:05 | Re: Exposing the Xact commit order to the user |