[COMMITTERS] pgsql: Doc wording improvement for NUMERIC limit paragraph.

2011-04-26 Thread Bruce Momjian
Doc wording improvement for NUMERIC limit paragraph. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dedcc48c567e443912d761a3616298678a4ec825 Modified Files -- doc/src/sgml/datatype.sgml |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) -- Sen

Re: [COMMITTERS] pgsql: Clarify that a non-specified precision NUMERIC has a very high r

2011-04-26 Thread Bruce Momjian
Tom Lane wrote: > Robert Haas writes: > > On Tue, Apr 26, 2011 at 1:28 PM, Bruce Momjian wrote: > >> I removed the extra "the", and I didn't think people were clear you > >> could just specify NUMERIC alone. ?We know you can you can do things > >> like VARCHAR, but others will probably not realiz

[COMMITTERS] pgsql: Reword documentation for NUMERIC with no specified precision.

2011-04-26 Thread Bruce Momjian
Reword documentation for NUMERIC with no specified precision. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/8ce83b5bdc532e716c39b6a04f1edda7e5e66cc7 Modified Files -- doc/src/sgml/datatype.sgml |7 +++ 1 files changed, 3 insertions(+), 4 deletion

[COMMITTERS] pgsql: Rephrase some not-supported error messages in pg_hba.conf proces

2011-04-26 Thread Tom Lane
Rephrase some not-supported error messages in pg_hba.conf processing. In a couple of places we said "not supported on this platform" for cases that aren't really platform-specific, but could depend on configuration options such as --with-openssl. Use "not supported by this build" instead, as that

[COMMITTERS] pgsql: Complain if pg_hba.conf contains "hostssl" but SSL is disabled.

2011-04-26 Thread Tom Lane
Complain if pg_hba.conf contains "hostssl" but SSL is disabled. Most commenters agreed that this is more friendly than silently failing to match the line during actual connection attempts. Also, this will prevent corner cases that might arise when trying to handle such a line when the SSL code is

[COMMITTERS] pgsql: Complain if pg_hba.conf contains "hostssl" but SSL is disabled.

2011-04-26 Thread Tom Lane
Complain if pg_hba.conf contains "hostssl" but SSL is disabled. Most commenters agreed that this is more friendly than silently failing to match the line during actual connection attempts. Also, this will prevent corner cases that might arise when trying to handle such a line when the SSL code is

[COMMITTERS] pgsql: Complain if pg_hba.conf contains "hostssl" but SSL is disabled.

2011-04-26 Thread Tom Lane
Complain if pg_hba.conf contains "hostssl" but SSL is disabled. Most commenters agreed that this is more friendly than silently failing to match the line during actual connection attempts. Also, this will prevent corner cases that might arise when trying to handle such a line when the SSL code is

Re: [COMMITTERS] pgsql: Clarify that a non-specified precision NUMERIC has a very high r

2011-04-26 Thread Tom Lane
Robert Haas writes: > On Tue, Apr 26, 2011 at 1:28 PM, Bruce Momjian wrote: >> I removed the extra "the", and I didn't think people were clear you >> could just specify NUMERIC alone.  We know you can you can do things >> like VARCHAR, but others will probably not realize it so I wanted to >> exp

Re: [COMMITTERS] pgsql: Clarify that a non-specified precision NUMERIC has a very high r

2011-04-26 Thread Robert Haas
On Tue, Apr 26, 2011 at 1:28 PM, Bruce Momjian wrote: > Robert Haas wrote: >> On Tue, Apr 26, 2011 at 11:55 AM, Bruce Momjian wrote: >> > Clarify that a non-specified precision NUMERIC has a very high range. >> >> This is entirely redundant.  You've added "(when the precision is not >> specified)

Re: [COMMITTERS] pgsql: Clarify that a non-specified precision NUMERIC has a very high r

2011-04-26 Thread Bruce Momjian
Robert Haas wrote: > On Tue, Apr 26, 2011 at 11:55 AM, Bruce Momjian wrote: > > Clarify that a non-specified precision NUMERIC has a very high range. > > This is entirely redundant. You've added "(when the precision is not > specified)" but that's exactly what the word "otherwise" already > conv

Re: [COMMITTERS] pgsql: Clarify that a non-specified precision NUMERIC has a very high r

2011-04-26 Thread Robert Haas
On Tue, Apr 26, 2011 at 11:55 AM, Bruce Momjian wrote: > Clarify that a non-specified precision NUMERIC has a very high range. This is entirely redundant. You've added "(when the precision is not specified)" but that's exactly what the word "otherwise" already conveys. -- Robert Haas Enterpris

[COMMITTERS] pgsql: Clarify that a non-specified precision NUMERIC has a very high r

2011-04-26 Thread Bruce Momjian
Clarify that a non-specified precision NUMERIC has a very high range. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/0cdbef6cec753a1606c2ce2955e3ff1005ed5ebf Modified Files -- doc/src/sgml/datatype.sgml |5 +++-- 1 files changed, 3 insertions(+), 2 de

[COMMITTERS] textsearch-ja - textsearch-ja: Added pure-mecab text parser and

2011-04-26 Thread User Itagaki
Log Message: --- Added pure-mecab text parser and configuration as "mecab". It is good at some composite words, but has issues with numerics and HTML document. Modified Files: -- textsearch-ja: textsearch_ja.c (r1.16 -> r1.17) (http://cvs.pgfoundry.org/cgi

[COMMITTERS] pgsql: Now that pg_upgrade uses -w in pg_ctl, remove loop that retried

2011-04-26 Thread Bruce Momjian
Now that pg_upgrade uses -w in pg_ctl, remove loop that retried testing the connection; also restructure the libpq connection code. This patch also removes the unused variable postmasterPID and fixes a libpq structure leak that was in the testing loop. Branch -- master Details --- http:

[COMMITTERS] textsearch-ja - textsearch-ja: Fix a bug in text normalization when a

2011-04-26 Thread User Itagaki
Log Message: --- Fix a bug in text normalization when a document begins with a single byte character followed by multibyte characters. Modified Files: -- textsearch-ja: textsearch_ja.c (r1.15 -> r1.16) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/textsearch