On Fri, Jan 25, 2013 at 01:42:48PM -0500, Tom Lane wrote:
> Bruce Momjian <[email protected]> writes:
> > On Fri, Jan 25, 2013 at 01:35:49PM -0500, Tom Lane wrote:
> >> This patch seems pretty bizarre. What is the difference between a
> >> "configuration parameter" and a "run-time setting"? Why would you
> >> point people to two different places for those two terms?
>
> > Should I make them both "configuration parameter" and leave the
> > "security" as a second one separate?
>
> Works for me. I think "configuration parameter" is the phrase we
> use most places.
OK, attached patch applied.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
new file mode 100644
index 929d29c..f869b50
*** a/doc/src/sgml/ddl.sgml
--- b/doc/src/sgml/ddl.sgml
*************** CREATE TABLE public.products ( ... );
*** 1736,1742 ****
<indexterm>
<primary><varname>search_path</varname></primary>
! <secondary>run-time setting</secondary>
</indexterm>
<para>
--- 1736,1742 ----
<indexterm>
<primary><varname>search_path</varname></primary>
! <secondary>configuration parameter</secondary>
</indexterm>
<para>
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
