From c4465095659bb089e08f8c94ce045ba3572a194f Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Thu, 22 Jun 2000 22:31:24 +0000 Subject: Second pass over run-time configuration system. Adjust priorities on some option settings. Sort out SIGHUP vs BACKEND -- there is no total ordering here, so make explicit checks. Add comments explaining all of this. Removed permissions check on SHOW command. Add examine_subclass to the game, rename to SQL_inheritance to fit the official data model better. Adjust documentation. Standalone backend needs to reset all options before it starts. To facilitate that, have IsUnderPostmaster be set by the postmaster itself, don't wait for the magic -p switch. Also make sure that all environment variables and argv's survive init_ps_display(). Use strdup where necessary. Have initdb make configuration files (postgresql.conf, pg_hba.conf) mode 0600 -- having configuration files is no fun if you can't edit them. --- doc/src/sgml/advanced.sgml | 35 +++++++++++++++++++---------------- doc/src/sgml/inherit.sgml | 34 ++++++++++++++++++++-------------- doc/src/sgml/ref/select.sgml | 4 ++-- doc/src/sgml/runtime.sgml | 19 ++++++++++++++++++- 4 files changed, 59 insertions(+), 33 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml index 2807c8bc86b..1cf2c63ffab 100644 --- a/doc/src/sgml/advanced.sgml +++ b/doc/src/sgml/advanced.sgml @@ -1,5 +1,5 @@ @@ -116,22 +116,25 @@ SELECT name, altitude support this ONLY notation. - - Deprecated: In previous versions of postgres, the default was not to - get access to child classes. By experience this was found to be error - prone. Under the old syntax, to get the sub-classes you append "*" - to the table name. For example - - + + Deprecated + + In previous versions of Postgres, the + default was not to get access to child tables. This was found to + be error prone and is also in violation of SQL. Under the old + syntax, to get the sub-classes you append "*" to the table name. + For example + SELECT * from cities*; - - - This old behaviour is still available by using a SET command: - - -SET EXAMINE_SUBCLASS TO on; - - + + To get the old behavior, the set configuration option + SQL_Inheritance to off, e.g., + +SET SQL_Inheritance TO OFF; + + or add a line in your postgresql.conf file. + + diff --git a/doc/src/sgml/inherit.sgml b/doc/src/sgml/inherit.sgml index 73a2678655d..774795f94d9 100644 --- a/doc/src/sgml/inherit.sgml +++ b/doc/src/sgml/inherit.sgml @@ -1,5 +1,5 @@ @@ -96,19 +96,25 @@ CREATE TABLE capitals UNDER cities ( UPDATE and DELETE -- support this ONLY notation. - - Deprecated: In previous versions of postgres, the default was not to - get access to child classes. By experience this was found to be error - prone. Under the old syntax, to get the sub-classes you append "*" - to the table name. For example - - SELECT * from cities*; - - This old behaviour is still available by using a SET command... - - SET EXAMINE_SUBCLASS TO on; - - + + Deprecated + + In previous versions of Postgres, the + default was not to get access to child tables. This was found to + be error prone and is also in violation of SQL. Under the old + syntax, to get the sub-classes you append "*" to the table name. + For example + +SELECT * from cities*; + + To get the old behavior, the set configuration option + SQL_Inheritance to off, e.g., + +SET SQL_Inheritance TO OFF; + + or add a line in your postgresql.conf file. + + @@ -208,7 +208,7 @@ SELECT [ ALL | DISTINCT [ ON ( expression* to the table name. The old behaviour is available via the command - SET EXAMINE_SUBCLASS TO 'on'; + SET SQL_Inheritance TO OFF; diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index b92a1cc67b2..1f9a940aa00 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -914,6 +914,23 @@ env PGOPTIONS='--geqo=off' psql + + + SQL_INHERITANCE (bool) + + + This controls the inheritance semantics, in particular whether + subtables are included into the consideration of various + commands by default. This was not the case in versions prior + to 7.1. If you need this behaviour you can set this variable + to off, but in the long run you are encouraged to change your + applications to use the ONLY keyword to + exclude subtables. See the SQL language reference and the + User's Guide for more information about + inheritance. + + + -- cgit v1.2.3