I wrote this entry for planet postgreql back in 2008. I am posting it here again not to lose it. The details here are a bit out of date but some of them might still be relevant.
Autovacuum, something that comes up a lot when you talk about PostgreSQL maintainence, and it is relatively new, started from PostgreSQL 8.1 to be part of the backend proper. Before that it was a contrib module IIRC. In the generally excellent PotgreSQL documentation you can find its reference here however i will also try and state a few things about autovaccum which are not in docs but perhaps should be, i will also try to keep it as end-userish as possible. Continue reading
I have been confused about this for half a month until i figured this out. So what is Anti-Caching? And why is it needed? How is it different from the traditional buffer-pool system in all the databases today?
Dr. Stonebraker gave a talk where a small part of it talks about “Anti-Caching”. It is supposed to be a better way to use memory with databases dealing in large datasets
Based on different parameters, reuirements etc you have the following popular options.
- Block level replication – DRBD
- PostgreSQL Streaming replication (SR)– only available 9.0 +
- Slony Trigger based replication – Almost the gold standard for Master – Slave replication
- Bucardo – Perl based multi master Async replication
- pgPool- II – Load balancer, Query cache, connection pooller , Replication manager
- pgCluster – multi-master synchronous replication