Skip site navigation (1) Skip section navigation (2)

Re: Decreasing WAL size effects

From: Greg Smith <gsmith(at)gregsmith(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, Kyle Cordes <kyle(at)kylecordes(dot)com>, pgsql <pgsql-general(at)postgresql(dot)org>
Subject: Re: Decreasing WAL size effects
Date: 2008-10-31 01:18:08
Message-ID: Pine.GSO.4.64.0810302114190.18447@westnet.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
On Thu, 30 Oct 2008, Tom Lane wrote:

> The real reason not to put that functionality into core (or even
> contrib) is that it's a stopgap kluge.  What the people who want this
> functionality *really* want is continuous (streaming) log-shipping, not
> WAL-segment-at-a-time shipping.

Sure, and that's why I didn't care when this got kicked out of the March 
CommitFest; was hoping a better one would show up.  But if 8.4 isn't going 
out the door with the feature people really want, it would be nice to at 
least make the stopgap kludge more easily available.

--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD

In response to

Responses

pgsql-hackers by date

Next:From: Dann CorbitDate: 2008-10-31 01:28:26
Subject: Re: Strange query behavior where clause produces odd behavior on '>' query
Previous:From: Robert HaasDate: 2008-10-31 01:04:27
Subject: Re: Sun Studio compiler warnings

pgsql-general by date

Next:From: Jason LongDate: 2008-10-31 01:29:24
Subject: Re: Decreasing WAL size effects
Previous:From: Scott MarloweDate: 2008-10-31 00:12:29
Subject: Re: Are there plans to add data compression feature to postgresql?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group