Prev: [HACKERS] MonetDB test says that PostgreSQL often has errors or missing results
Next: [HACKERS] Patch rev 2: MySQL-ism help patch for psql
From: Josh Berkus on 19 Jan 2010 17:30
Hackers,

So, here's a must-fix item for SR for release: we need adequate docs.
I'm happy to write these but *I* need to understand the answers first.

The current docs and wiki page do not explain:

* How (technically) the slave listens for LSNs
* Does the walreceiver need the archive (via archive_command) copies of
the WAL files after it's caught up with the master?
** If not, then what are we supposed to do with them? Write a cron job
to delete them every minute?
** If so, can we somehow use pg_standby with SR?

I've tried to dig this information out of the wiki and mailing list
archives and can't quite figure it out. Is there a tech doc which was
not posted anywhere public, or do I need to just RTFC?

Also, given that recovery.conf has become a key part of our replication,
shouldn't we supply a recovery.example file which people can rename and
edit? Happy to write this too.

--Josh Berkus


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] MonetDB test says that PostgreSQL often has errors or missing results
Next: [HACKERS] Patch rev 2: MySQL-ism help patch for psql