Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: making postgres DB stable, efficient and secure
- From: Jeff Davis <pgsql(at)j-davis(dot)com>
- To: Jasbinder Singh Bali <jsbali(at)gmail(dot)com>
- Cc: pgsql-general(at)postgresql(dot)org
- Subject: Re: making postgres DB stable, efficient and secure
- Date: Thu, 22 Mar 2007 15:30:37 -0700
- Message-id: <1174602637(dot)23455(dot)569(dot)camel(at)dogma(dot)v10(dot)wvs>
On Thu, 2007-03-22 at 16:59 -0400, Jasbinder Singh Bali wrote: > Hi, > I'm done with my database design and almost got it working (with all > triggers and functions) pefectly. > Now, i need to see how can I make my DB stable, efficient and secure. > > I wanted to know how should I go about it as far as postgres is > concerned > What are the best practices is this regard. > > Any kind of help would be higly appreciated. > (1) Run it on a stable OS (2) Disable write cache on your disks, and make *sure* it's disabled The rest of your question is quite open-ended. Start with the default configuration, read the documentation, experiment on a separate box you don't care about, and you're on the right track. Regards, Jeff Davis
- References:
- making postgres DB stable, efficient and secure
- From: Jasbinder Singh Bali
- making postgres DB stable, efficient and secure
- Prev by Date: database-wide triggers
- Next by Date: Every user has own database - how?
- Previous by thread: Re: making postgres DB stable, efficient and secure
- Next by thread: cutting out the middleperl
- Indexes: