More indenting cleanup for release notes.
This commit is contained in:
parent
35dab98e1b
commit
6fe5885cdf
@ -1,4 +1,4 @@
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.527 2007/10/18 23:34:54 momjian Exp $ -->
|
||||
<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.528 2007/10/19 01:56:06 momjian Exp $ -->
|
||||
<!--
|
||||
|
||||
Typical markup:
|
||||
@ -804,6 +804,7 @@ do it for earlier branch release files.
|
||||
point-in-time recovery.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
New boolean configuration parameter, <varname>archive_mode</>,
|
||||
@ -2436,6 +2437,7 @@ do it for earlier branch release files.
|
||||
<varname>search_path</>, and disable searching it for functions
|
||||
and operators (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
This is needed to allow a security-definer function to set a
|
||||
truly secure value of <varname>search_path</>. Without it,
|
||||
@ -2620,6 +2622,7 @@ do it for earlier branch release files.
|
||||
Remove security vulnerabilities that allowed connected users
|
||||
to read backend memory (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The vulnerabilities involve suppressing the normal check that a SQL
|
||||
function returns the data type it's declared to, and changing the
|
||||
@ -2648,6 +2651,7 @@ do it for earlier branch release files.
|
||||
Properly handle <function>to_char('CC')</> for years ending in
|
||||
<literal>00</> (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Year 2000 is in the twentieth century, not the twenty-first.
|
||||
</para>
|
||||
@ -2664,6 +2668,7 @@ do it for earlier branch release files.
|
||||
Fix incorrect permission check in
|
||||
<literal>information_schema.key_column_usage</> view (Tom)
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The symptom is <quote>relation with OID nnnnn does not exist</> errors.
|
||||
To get this fix without using <command>initdb</>, use <command>CREATE OR
|
||||
|
Loading…
x
Reference in New Issue
Block a user