On 08/09/2012 04:24 AM, Kevin Grittner wrote:
http://wiki.postgresql.org/wiki/Number_Of_Database_Connections
Can we please please PLEASE link to that as a comment above max_connections?
Last time this came up nobody was happy with wording of a comment so
nothing got done. It's a real usabil
Radovan Jablonovsky wrote:
> PostgreSQL version 9.1.1 with 32GB of RAM
> shared_buffers = 8GB
> temp_buffers = 32MB
> work_mem = 64MB
> maintenance_work_mem = 512MB
> Currently there are maximum 600 connections.
Please read:
http://wiki.postgresql.org/wiki/Number_Of_Database_Connections
Currently there are maximum 600 connections.
On Fri, Aug 3, 2012 at 2:05 PM, Scott Marlowe wrote:
> On Fri, Aug 3, 2012 at 12:08 PM, Radovan Jablonovsky
> wrote:
> > Thanks you for your response.
> >
> > Database config:
> > shared_buffers = 8GB
> > temp_buffers = 32MB
> > work_mem = 64MB
> > ma
Hi there,
And why not shipping older WAL files to the target on a regular basis ?.
On the master you can control with a crontab job to ship the wanted WAL
files (n hours older than current time and clean the shipped up, check
rsync options up) in a regular basis.
A.A.
On 07/26/2012 02:24 A
Hi.
I'm trying to work out failover and disaster recovery procedures for a
cluster of three servers. Streaming replication is being used with a high
wal_keep_segments, no log shipping is happening. I need to avoid the
several hours it takes to rebuild a hot standby from scratch.
ServerA is the ma
