Re: draft RFC: concept for partial, wal-based replication

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: draft RFC: concept for partial, wal-based replication
Date: 2009-11-30 11:23:57
Message-ID: 3B251FC6-6E25-4CAF-AA1B-98B8A3B1DE73@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Nov 30, 2009, at 1:55 AM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au> wrote:

> Boszormenyi Zoltan wrote:
>
>> c. splitting wal into different replication sets
>
> Just a side note: in addition to its use for partial replication, this
> might have potential for performance-prioritizing databases or
> tablespaces.
>
> Being able to separate WAL logging so that different DBs, tablespaces,
> etc went to different sets of WAL logs would allow a DBA to give some
> databases or tablespaces dedicated WAL logging space on faster
> storage.
> If partial recovery is implemented, it might also permit less
> important
> databases to be logged to fast-but-unsafe storage such as a non-BBU
> disk
> controller with write cache enabled, without putting more important
> databases in the same cluster in danger.

The danger here is that if we make crash recovery more complex, we'll
introduce subtle bugs that will only be discovered after someone's
data is toast.

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-11-30 12:06:18 Re: Patch: Remove gcc dependency in definition of inline functions
Previous Message Andrew Gierth 2009-11-30 10:34:08 Re: Aggregate ORDER BY patch