Re: Core team statement on replication in PostgreSQL

From: "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com>
To: "Gregory Stark" <stark(at)enterprisedb(dot)com>
Cc: "Greg Smith" <gsmith(at)gregsmith(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Andreas 'ads' Scherbaum" <adsmail(at)wars-nicht(dot)de>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Core team statement on replication in PostgreSQL
Date: 2008-06-10 10:03:08
Message-ID: 484E515C.5060309@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

Gregory Stark wrote:
> Instead of zeroing bytes and depending on compression why not just pass an
> extra parameter to the archive command with the offset to the logical end of
> data.

Because the archiver process doesn't have that information.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Josh Berkus 2008-06-10 16:01:05 Re: Core team statement on replication in PostgreSQL
Previous Message Gregory Stark 2008-06-10 09:43:51 Re: Core team statement on replication in PostgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-06-10 10:10:18 Re: Overhauling GUCS
Previous Message 汪琦 2008-06-10 09:50:03 why copy tuple in the end of trigger when nothing changed in NEW, OLD record variable