From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, pgsql-hackers(at)postgresql(dot)org, Gregory Stark <stark(at)enterprisedb(dot)com>, Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
Subject: | Re: Permanent settings |
Date: | 2008-02-20 23:38:09 |
Message-ID: | 200802202338.m1KNc9X11833@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Aidan Van Dyk wrote:
-- Start of PGP signed section.
> * Josh Berkus <josh(at)agliodbs(dot)com> [080220 18:00]:
> > All,
> >
> > I think we're failing to discuss the primary use-case for this, which
> > is one reason why the solutions aren't obvious.
>
> > However, imagine you're adminning 250 PostgreSQL servers backing a
> > social networking application. You decide the application needs a
> > higher default sort_mem for all new connections, on all 250 servers.
> > How, exactly, do you deploy that?
> >
> > Worse, imagine you're an ISP and you have 250 *differently configured*
> > PostgreSQL servers on vhosts, and you need to roll out a change in
> > logging destination to all machines while leaving other settings
> > untouched.
>
> But, from my experience, those are "pretty much" solved, with things
> like rsync, SCM (pick your favourite) and tools like "clusterssh,
> multixterm", rancid, wish, expect, etc.
Agreed. Put postgresql.conf on an NFS server and restart the servers.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-20 23:38:10 | Re: Permanent settings |
Previous Message | Aidan Van Dyk | 2008-02-20 23:17:37 | Re: Permanent settings |