1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
5 >Database Configuration</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 HREF="mailto:pgsql-docs@postgresql.org"><LINK
12 TITLE="PostgreSQL 7.4.1 Documentation"
13 HREF="index.html"><LINK
15 TITLE="Managing Databases"
16 HREF="managing-databases.html"><LINK
18 TITLE="Template Databases"
19 HREF="manage-ag-templatedbs.html"><LINK
21 TITLE="Alternative Locations"
22 HREF="manage-ag-alternate-locs.html"><LINK
25 HREF="stylesheet.css"><META
27 CONTENT="2003-12-22T03:48:47"></HEAD
33 SUMMARY="Header navigation table"
43 >PostgreSQL 7.4.1 Documentation</TH
51 HREF="manage-ag-templatedbs.html"
60 HREF="managing-databases.html"
67 >Chapter 18. Managing Databases</TD
73 HREF="managing-databases.html"
81 HREF="manage-ag-alternate-locs.html"
95 NAME="MANAGE-AG-CONFIG"
96 >18.4. Database Configuration</A
100 HREF="runtime-config.html"
106 > server provides a large number of
107 run-time configuration variables. You can set database-specific
108 default values for many of these settings.
111 > For example, if for some reason you want to disable the
115 > optimizer for a given database, you'd
116 ordinarily have to either disable it for all databases or make sure
117 that every connecting client is careful to issue <TT
121 >. To make this setting the default you can
124 CLASS="PROGRAMLISTING"
125 >ALTER DATABASE mydb SET geqo TO off;</PRE
127 This will save the setting (but not set it immediately) and in
128 subsequent connections it will appear as though <TT
132 > had been called right before the session started.
133 Note that users can still alter this setting during the session; it
134 will only be the default. To undo any such setting, use
153 SUMMARY="Footer navigation table"
164 HREF="manage-ag-templatedbs.html"
182 HREF="manage-ag-alternate-locs.html"
192 >Template Databases</TD
198 HREF="managing-databases.html"
206 >Alternative Locations</TD