Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby
Date: 2009-07-07 21:33:31
Message-ID: 28650.1247002411@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dimitri Fontaine <dfontaine(at)hi-media(dot)com> writes:
> Could we add yet another postmaster specialized child to handle the
> archive, which would be like a default archive_command implemented in
> core.

I think this fails the basic sanity check: do you need it to still work
when the master is dead. It's reasonable to ask the master to supply a
few gigs of very-recent WAL, but as soon as the word "archive" enters
the conversation, you should be thinking in terms of a different
machine. Or at least a design that easily scales to put the archive on
a different machine.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-07-07 21:35:46 Re: *_collapse_limit, geqo_threshold
Previous Message Sergey Burladyan 2009-07-07 21:14:49 Re: 8.4, One-Time Filter and subquery ( ... FROM function() union all ... )