Postgres Pro
Downloads
Home   >   mailing lists

Re: Keeping separate WAL segments for each database - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Keeping separate WAL segments for each database
Date
Msg-id 1278168390.4151.7979.camel@ebony
Whole thread Raw
In response to Re: Keeping separate WAL segments for each database  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Keeping separate WAL segments for each database
List pgsql-hackers
Tree view 
On Wed, 2010-06-30 at 22:21 -0400, Tom Lane wrote:

> What about having a single WAL stream for all commit records (thereby
> avoiding any possible xact-serialization funnies) and other WAL
> records
> divided up among multiple streams in some fashion or other?  A commit
> record would bear minimum-LSN pointers for all the streams that its
> transaction had written to.  Things like HEAP_CLEAN records would bear
> minimum-LSN pointers for the commit stream.  Workable?

I'm interested in the idea of putting full page writes into one stream
and all other WAL records into another.

That would allow us to stream less data for log shipping.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Development, 24x7 Support, Training and Services

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: nvarchar notation accepted?
Next
From: Tom Lane
Date:
Subject: Re: Keepalive for max_standby_delay