Re: [COMMITTERS] pgsql: Clarify description of CIDR-address column

2006-11-17 Thread Andrew Dunstan
Tom Lane wrote: > Log Message: > --- > Clarify description of CIDR-address column of pg_hba.conf, to discourage > people from trying notations like '10.6/16', which is accepted but does > not mean what you probably think. Per example from Paul Forgey. > Isn't the real problem here that 10

[COMMITTERS] pgsql: Clarify description of CIDR-address column of pg_hba.conf, to

2006-11-17 Thread Tom Lane
Log Message: --- Clarify description of CIDR-address column of pg_hba.conf, to discourage people from trying notations like '10.6/16', which is accepted but does not mean what you probably think. Per example from Paul Forgey. Modified Files: -- pgsql/doc/src/sgml:

[COMMITTERS] pgimport - pgimport: * some more examples, one containing failures *

2006-11-17 Thread User Dim
Log Message: --- * some more examples, one containing failures * configurable null and empty_string representations * bugfix on newline_escapes behavior when all lines are not escaped * new global newline_escapes setting * uses by default psycopg2, failback to psycopg1 if not available * cl

[COMMITTERS] pgsql: Repair two related errors in heap_lock_tuple: it was failing to

2006-11-17 Thread Tom Lane
Log Message: --- Repair two related errors in heap_lock_tuple: it was failing to recognize cases where we already hold the desired lock "indirectly", either via membership in a MultiXact or because the lock was originally taken by a different subtransaction of the current transaction. Thes

[COMMITTERS] pgsql: Repair two related errors in heap_lock_tuple: it was failing to

2006-11-17 Thread Tom Lane
Log Message: --- Repair two related errors in heap_lock_tuple: it was failing to recognize cases where we already hold the desired lock "indirectly", either via membership in a MultiXact or because the lock was originally taken by a different subtransaction of the current transaction. Thes

[COMMITTERS] pgsql: Small message equalization fix

2006-11-17 Thread Peter Eisentraut
Log Message: --- Small message equalization fix Modified Files: -- pgsql/src/backend/executor: execQual.c (r1.198 -> r1.199) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/execQual.c.diff?r1=1.198&r2=1.199) -

[COMMITTERS] pgsql: Rename replication section "High Availability and Load

2006-11-17 Thread Bruce Momjian
Log Message: --- Rename replication section "High Availability and Load Balancing". Modified Files: -- pgsql/doc/src/sgml: filelist.sgml (r1.48 -> r1.49) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/filelist.sgml.diff?r1=1.48&r2=1.49)

[COMMITTERS] pgsql: Data Partitioning documentation section reduced and moved to the

2006-11-17 Thread Bruce Momjian
Log Message: --- Data Partitioning documentation section reduced and moved to the end. Modified Files: -- pgsql/doc/src/sgml: failover.sgml (r1.12 -> r1.13) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/failover.sgml.diff?r1=1.12&r2=1.13)

Re: [COMMITTERS] pgsql: Fixed small typo, missing 'l' in 'Cluserting'

2006-11-17 Thread Markus Schiltknecht
Hi, Michael Meskes wrote: missing 'l' in 'Cluserting' ROTFL.. what do you miss in Cluserting? It's all there ;-) No offense. Patch is all right. Thank you for the early-morning-giggle. Regards Markus ---(end of broadcast)--- TIP 2: Don't 'kil

[COMMITTERS] pgsql: Fix a typo.

2006-11-17 Thread Neil Conway
Log Message: --- Fix a typo. Modified Files: -- pgsql/doc/src/sgml: failover.sgml (r1.11 -> r1.12) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/failover.sgml.diff?r1=1.11&r2=1.12) ---(end of broadcast)-

[COMMITTERS] pgsql: Fixed small typo, missing 'l' in 'Cluserting'

2006-11-17 Thread Michael Meskes
Log Message: --- Fixed small typo, missing 'l' in 'Cluserting' Modified Files: -- pgsql/doc/src/sgml: failover.sgml (r1.10 -> r1.11) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/failover.sgml.diff?r1=1.10&r2=1.11)