Hannu Krosing wrote:
> The simplest form of synchronous wal shipping would not even need
> postgresql running on slave, just a small daemon which
> reports when wal
> blocks are a) received and b) synced to disk.
While that does sound simple, I'd presume that most people would want the guarantee of the same version of postgresql installed wherever the logs are ending up, with the log receiver speaking the same protocol version as the log sender. I imagine that would be most easily achieved through using something like the continuously restoring startup mode of current postgresql.
However variations on this kind of daemon can be used to perform testing, configuring it to work well, go slow, pause, not respond, disconnect, or fail in particular ways, emulating disk full, etc.
At the Datamail Group we value teamwork, respect, achievement, client focus, and courage.
This email with any attachments is confidential and may be subject to legal privilege.
If it is not intended for you please advise by replying immediately, destroy it and do not
copy, disclose or use it in any way.
The Datamail Group, through our GoGreen programme, is committed to environmental sustainability.
Help us in our efforts by not printing this email.
This email has been scanned by the DMZGlobal Business Quality
Electronic Messaging Suite.
Please see http://www.dmzglobal.com/dmzmessaging.htm for details.
In response to
pgsql-hackers by date
|Next:||From: Martijn van Oosterhout||Date: 2008-06-04 04:35:40|
|Subject: Re: Case-Insensitve Text Comparison|
|Previous:||From: Tom Lane||Date: 2008-06-04 04:06:17|
|Subject: Re: Case-Insensitve Text Comparison |
pgsql-advocacy by date
|Next:||From: Koichi Suzuki||Date: 2008-06-04 04:16:01|
|Subject: Re: International quality standards|
|Previous:||From: Andrew Sullivan||Date: 2008-06-04 03:20:11|
|Subject: Re: Core team statement on replication in PostgreSQL|