On Thu, May 10, 2012 at 12:41:17PM +0530, Gnanakumar wrote:
> > There have been numerous discussions of this on the lists, so you
> > can probably find a more in-depth discussion of the topic if you
> > search the archives, and this may motivate me to put together a Wiki
> > page on the topic, but
Hi Everybody,
I am testing the new features in 9.1 related to backups and restores.
I want to establish a workflow for doing a base backup, archiving wals for a
primary server and be able to restore the primary server from those.
Testing Environment:
Testing on Windows Server 2008 R2
Postgresql.
"Gnanakumar" wrote:
> I've already thought of converting this into a document and keep
> it handy so that I may want to refer back whenever I need.
I've put up a first cut at such a document as a Wiki page:
http://wiki.postgresql.org/wiki/Number_Of_Database_Connections
Everyone should feel
> A formula which has held up pretty well across a lot of benchmarks
> for years is that for optimal throughput the number of active
> connections should be somewhere near
> ((core_count * 2) + effective_spindle_count).
Our entire Production application stack is setup in Amazon EC2 cloud
enviro
> There have been numerous discussions of this on the lists, so you
> can probably find a more in-depth discussion of the topic if you
> search the archives, and this may motivate me to put together a Wiki
> page on the topic, but here's the general concept.
I was really astonished on seeing a gre
