Prev: [COMMITTERS] pgsql: Un-break pg_dump for the case ofzero-column tables.
Next: BUG #4887: inclusion operator (@>) on tsqeriesbehaves not conforming to documentation
From: Fujii Masao on 24 Feb 2010 11:59
On Tue, Dec 22, 2009 at 11:25 AM, Fujii Masao <masao.fujii(a)gmail.com> wrote:
> I found there is no "primary" tag for the HS parameters
> in config.sgml. Attached patch adds that tag.

I found another small problem in HS doc; though the type of
trace_recovery_messages is actually enum, it's described as
string in the doc. The attached patch does s/string/emum.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From: Bruce Momjian on 27 Feb 2010 09:44
Fujii Masao wrote:
> On Tue, Dec 22, 2009 at 11:25 AM, Fujii Masao <masao.fujii(a)gmail.com> wrote:
> > I found there is no "primary" tag for the HS parameters
> > in config.sgml. Attached patch adds that tag.
>
> I found another small problem in HS doc; though the type of
> trace_recovery_messages is actually enum, it's described as
> string in the doc. The attached patch does s/string/emum.

Thanks, applied.

--
Bruce Momjian <bruce(a)momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [COMMITTERS] pgsql: Un-break pg_dump for the case ofzero-column tables.
Next: BUG #4887: inclusion operator (@>) on tsqeriesbehaves not conforming to documentation