Re: Permanent settings - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Permanent settings
Date
Msg-id 200802202338.m1KNc9X11833@momjian.us
Whole thread Raw
In response to Re: Permanent settings  (Aidan Van Dyk <aidan@highrise.ca>)
Responses Re: Permanent settings
Re: Permanent settings
List pgsql-hackers
Aidan Van Dyk wrote:
-- Start of PGP signed section.
> * Josh Berkus <josh@agliodbs.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@momjian.us>        http://momjian.us EnterpriseDB
http://postgres.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Permanent settings
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: Which MemoryContext?