On 01/02/14 16:12, Tory M Blue wrote:
> We are getting outside of slon and into postgres and i'll try to keep
> this light, here are my postgresql custom config aspects

Postgres and its architecture very much affect the behavior and
performance of Slony. I'm afraid that they cannot be viewed completely
isolate from each other.

> The hardware is being refreshed but right now it's an 8 core, 32GB
> CentOS system, being replaced with some pretty big hardware
> 256GB/32cores many SSD's. But tuning this now and knowing where I need
> to tweak when I add the added capacity would be great.

The slon process uses one single database connection to the data
provider for the copy operation and another single database connection
to feed the data into the new replica. A single Postgres session only
utilizes one single core. It therefore makes zero difference if you are
upgrading from a dual core to 64 cores or more.

The suggestions made about work mem and maintenance work mem are valid.
If you are using a dedicated DB user for all your slon database
connections you can tweak these per server via ALTER USER.


Regards,
Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin