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 <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
