BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation








EnterpriseDB: Runtime Configuration

Oracle Tips by Burleson Consulting

EnterpriseDB provides a huge amount of configurability.  I am not going to cover every possible configuration item that you might come across.  I will cover those items that I think are most important to your usage of EnterpriseDB in a day-to-day environment. 

EnterpriseDB uses several files for configuration.  By default, all of these files are in the default data directory for the cluster.  Runtime configuration is controlled by the postgresql.conf file. The postgresql.conf file also includes security options but security access controls are in the pg_hba.conf and pg_ident.conf files.

Any time you change configuration or security settings, you need to restart the server.  You may do this using the pg_ctl (discussed above) command line utility or choose Restart Database under the Expert Configuration option of the EnterpriseDB menu.


Table 2.1 lists some of the more important runtime configuration options.





The default directory where EnterpriseDB will store data.  Set during installation.



Host Based Authentication file.  Authentication for IP and user access.



Ident authentication.




A list of IP addresses that the database will listen for connections.  To secure your system you can limit this to only certain addresses.  The keyword localhost will only allow local connections and using an * will allow connections from any address.  If you want to limit by IP, you can set this to * and use the pg_hba.conf file.




Server TCP port that will be used to listen for connections.






Maximum number of concurrent connections.  Each connection requires memory even if the connection is not being used.




Enable ssl connections.



Encrypt user passwords.






Automatic resource tuning.  A very handy feature.  For development and testing it is a set it and forget about it feature.  For production you may want to tweak this parameter to get the best performance.

This value can be any number between 0 and 100.  If you set it to 1 EnterpriseDB will try to only use the least amount of available system resources.  Set it to 100 and EnterpriseDB will use the maximum amount of system resources.  If set to 0, automatic resource tuning is turned off.

The default is set during installation.  33% for development, 66% for mixed server and 100% for dedicated server.





This option sets the program that will be used to archive log files.  If it is empty, the database is not in archive log mode and that is a bad thing.  This program can be any third party utility or shell command.  It can be as simple as a cp or COPY command.






This option will tell the optimizer to use check constraints when optimizing queries.  This will need to be on if you use partitioned tables.






Type of system logging to enable, stderr, syslog (Linux), or the event log (MS-Windows).

stderr & syslog (Linux) or eventlog (MS-Windows)



Allow stderr to be redirected to a file.



Directory to store system log files.




Log file name as stored in the OS.  The file name can contain certain parameters:

%Y = Year

%m = Month

%d = day

%H = hour

%M = minute

%S = Second


will create a file name like:







Size the system log file should be allowed to grow to before starting a new file.




The minimal level of message logging.  Values are DEBUG5-1, INFO, NOTICE, WARNING, and ERROR.  In a development environment, you may want to log at a DEBUG level.  In production, you may want to generate fewer messages.






Allows statistical information to be collected.






Collects statistics on each command that is run.  Set this to On.




Database block level statistics.  Set this on.




Row level statistics.  Set this to on.







Automatically clean up updated and deleted rows.  Should be set to on.





How should EnterpriseDB display dates.  Valid options are Redwood (DATE + TIME, DD-MON-YYYY), ISO, SQL or German. 





If on, creating a table with a DATE column will replace DATE with TIMESTAMP(0) so that DATE + TIME will be stored.  If this is off, the DATE will remain a DATE and no time component will be stored. 


Table 2.1 – Runtime Configuration Options

As I said, this minimal list covers those items you will want to be familiar with when first starting with EnterpriseDB.  It is well worth your time to take a look at the postgresql.conf file and read about the other available configuration options.

This is an excerpt from the book "EnterpriseDB: The Definitive Reference" by Rampant TechPress.

Expert Remote DBA

BC is America's oldest and largest Remote DBA Oracle support provider.  Get real Remote DBA experts, call
BC Remote DBA today.



Remote DBA Service

Oracle Tuning Book


Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software







BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.

Hit Counter