Re: Core team statement on replication in PostgreSQL

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Teodor Sigaev" <teodor(at)sigaev(dot)ru>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Core team statement on replication in PostgreSQL
Date: 2008-05-29 19:22:09
Message-ID: e51f66da0805291222w5a0928ebk3d96dfe5bd713c0a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers

On 5/29/08, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
> > in this case too. So each slave just needs to report its own longest
> > open tx as "open" to master. Yes, it bloats master but no way around it.
>
> Slaves should not report it every time or every transaction. Vacuum on
> master will ask them before doing a real work.

That is bit too slow if we want to do some page-level cleanup with
regular transactions / bgwriter. But once or twice per minute update
should work fine.

--
marko

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Andrew Sullivan 2008-05-29 19:30:07 Re: Core team statement on replication in PostgreSQL
Previous Message Brian Hurt 2008-05-29 19:21:24 Re: Core team statement on replication in PostgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Sullivan 2008-05-29 19:30:07 Re: Core team statement on replication in PostgreSQL
Previous Message Brian Hurt 2008-05-29 19:21:24 Re: Core team statement on replication in PostgreSQL