database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-28 05:21:27 +03:00
Code

Links to GUC variables from HISTORY don't work in back branches...

Browse Source
This commit is contained in:
Tom Lane 2007-01-06 06:01:37 +00:00
parent e677ff2876
commit c3013376b2
1 changed files with 5 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/src/sgml/release.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.36 2007/01/06 04:17:59 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.400.2.37 2007/01/06 06:01:37 tgl Exp $ -->
<!--
Typical markup:
@ -136,8 +136,7 @@ For new features, add links to the documentation sections.
</para>
<para>
This is because <link
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
This is because <varname>lc_numeric</> can potentially
change the output of these functions.
</para>
</listitem>
@ -2914,8 +2913,7 @@ psql -t -f fixseq.sql db1 | psql -e db1
</para>
<para>
This is because <link
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
This is because <varname>lc_numeric</> can potentially
change the output of these functions.
</para>
</listitem>
@ -6220,8 +6218,7 @@ typedefs (Michael)</para></listitem>
</para>
<para>
This is because <link
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
This is because <varname>lc_numeric</> can potentially
change the output of these functions.
</para>
</listitem>
@ -9236,8 +9233,7 @@ DROP SCHEMA information_schema CASCADE;
</para>
<para>
This is because <link
linkend="guc-lc-numeric"><varname>lc_numeric</></link> can potentially
This is because <varname>lc_numeric</> can potentially
change the output of these functions.
</para>
</listitem>