Database Reference
In-Depth Information
F High-availability plan
Decide what form of replication you'll need, if any
How it works...
One of the most important reasons for planning your database ahead of time is that
retrofitting some things is difficult. This is especially true of server encoding and locale,
which can cause much downtime and exertion if we need to change them later. Security
is also much more difficult to set up after the system is live.
There's more...
Planning always helps. You may know what you're doing, but others may not. Tell everybody
what you're going to do before you do it, to avoid wasting time. If you're not sure yet, then build
a prototype to help decideā€”approach the administration framework as if it were a development
task. Make a list of things you don't know yet, and work through them, one by one.
This is deliberately a very short recipe. Everybody has their own way of doing things, and it's
very important not to be too prescriptive about how to do things. If you already have a plan,
great. If you don't, think about what you need to do, make a checklist, and then do it.
Changing parameters in your programs
PostgreSQL allows you to set some parameter settings for each session or for each transaction.
How to do it...
You can change the value of a setting during your session, such as the following:
SET work_mem = '16MB';
This value will then be used for every future transaction. You can also change it only
for the duration of the "current transaction"
SET LOCAL work_mem = '16MB';
The setting will last until or if you issue the following:
RESET work_mem;
or
RESET ALL;
 
Search WWH ::




Custom Search