git.postgresql.org Git - postgresql.git/commitdiff

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml

index 370d68811a61b6fa6f2d3d4b6e15a0750dc2c7e2..653402247c09115a1334faaa67f5192cf42c60ca 100644 (file)

--- a/doc/src/sgml/release.sgml

+++ b/doc/src/sgml/release.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.590 2009年03月12日 22:35:48 tgl Exp $ -->

+<!-- $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.591 2009年03月17日 21:36:21 tgl Exp $ -->

<!--

Typical markup:

error. The solution therefore is to disable translation and encoding

conversion and report the plain-ASCII form of any error message,

if we find we have gotten into a recursive error reporting situation.

+ (CVE-2009-0922)

</para>

</listitem>

error. The solution therefore is to disable translation and encoding

conversion and report the plain-ASCII form of any error message,

if we find we have gotten into a recursive error reporting situation.

+ (CVE-2009-0922)

</para>

</listitem>

error. The solution therefore is to disable translation and encoding

conversion and report the plain-ASCII form of any error message,

if we find we have gotten into a recursive error reporting situation.

+ (CVE-2009-0922)

</para>

</listitem>

error. The solution therefore is to disable translation and encoding

conversion and report the plain-ASCII form of any error message,

if we find we have gotten into a recursive error reporting situation.

+ (CVE-2009-0922)

</para>

</listitem>

error. The solution therefore is to disable translation and encoding

conversion and report the plain-ASCII form of any error message,

if we find we have gotten into a recursive error reporting situation.

+ (CVE-2009-0922)

</para>

</listitem>