7.35b doc bug?

From: elein <elein(at)sbcglobal(dot)net>
To: pgsql-docs(at)postgresql(dot)org
Cc: elein(at)varlena(dot)com
Subject: 7.35b doc bug?
Date: 2002-11-20 21:40:59
Message-ID: 200211202142.gAKLgLtF663208@pimout2-ext.prodigy.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs


In 4.2 User Attributes, the word geqo should probably be changed to
enable_indexscan.

4.2 User Attributes...

A user can also set personal defaults for many of the run-time configuration settings described in
Section 3.4. For example, if for some reason you want to disable index scans
(hint: not a good idea) anytime you connect, you can use

ALTER USER myname SET enable_indexscan TO off;

This will save the setting (but not set it immediately) and in subsequent
connections it will appear as though SET geqo TO off; had been called right
before the session started.

This probably should read:

A user can also set personal defaults for many of the run-time configuration
settings described in Section 3.4. For example, if for some reason you want
to disable index scans (hint: not a good idea) anytime you connect, you can
use

ALTER USER myname SET enable_indexscan TO off;

This will save the setting (but not set it immediately) and in subsequent
connections it will appear as though SET enable_indexscan TO off; had been
called right before the session started.

elein(at)varlena(dot)com
--
------------------------------------------------------------------------------------------
elein(at)varlena(dot)com Database Consulting www.varlena.com
It's a doggie dog world.

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruno Wolff III 2002-11-22 14:00:47 7.3 rc1 timestamp description typos
Previous Message Peter Eisentraut 2002-11-17 13:24:34 Re: Column and table constraints - anally retentive comments