[COMMITTERS] pgsql: Fix multicolumn GIN's wrong results with fastupdate enabled.

2009-11-13 Thread Teodor Sigaev
Log Message:
---
Fix multicolumn GIN's wrong results with fastupdate enabled.
User-defined consistent functions believes the check array
contains at least one true element which was not a true for
scanning pending list.

Per report from Yury Don 

Modified Files:
--
pgsql/src/backend/access/gin:
ginget.c (r1.27 -> r1.28)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginget.c?r1=1.27&r2=1.28)

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


[COMMITTERS] pgsql: Fix multicolumn GIN's wrong results with fastupdate enabled.

2009-11-13 Thread Teodor Sigaev
Log Message:
---
Fix multicolumn GIN's wrong results with fastupdate enabled.
User-defined consistent functions believes the check array
contains at least one true element which was not a true for
scanning pending list.

Per report from Yury Don 

Tags:

REL8_4_STABLE

Modified Files:
--
pgsql/src/backend/access/gin:
ginget.c (r1.27 -> r1.27.2.1)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gin/ginget.c?r1=1.27&r2=1.27.2.1)

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


[COMMITTERS] pgbouncer - pgbouncer: Disable maintenance during SUSPEND Otherwise

2009-11-13 Thread User Mkz
Log Message:
---
Disable maintenance during SUSPEND

Otherwise some timeout may activate and close connection
that is already reported to other side;

Modified Files:
--
pgbouncer/src:
janitor.c (r1.34 -> r1.35)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/janitor.c?r1=1.34&r2=1.35)

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


[COMMITTERS] pgbouncer - pgbouncer: Clarify few login-related log messages

2009-11-13 Thread User Mkz
Log Message:
---
Clarify few login-related log messages

Modified Files:
--
pgbouncer/src:
client.c (r1.26 -> r1.27)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/src/client.c?r1=1.26&r2=1.27)

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


[COMMITTERS] pgbouncer - pgbouncer: win32: allow user to override service account

2009-11-13 Thread User Mkz
Log Message:
---
win32: allow user to override service account

The automatic decision between Local System and Local Service
was not reliable enough.  And anyway, it's better to let user
pick proper account.

Modified Files:
--
pgbouncer/win32:
win32support.c (r1.7 -> r1.8)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/win32/win32support.c?r1=1.7&r2=1.8)

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


[COMMITTERS] pgsql: When you do "ARRAY[...]::domain", where domain is a domain over

2009-11-13 Thread Heikki Linnakangas
Log Message:
---
When you do "ARRAY[...]::domain", where domain is a domain over an array type,
we need to check domain constraints. We used to do it correctly, but 8.4
introduced a separate code path for the "ARRAY[]::arraytype" case to infer
the type of an empty ARRAY construct from the cast target, and forgot to take
domains into account.

Per report from Florian G. Pflug.

Modified Files:
--
pgsql/src/backend/parser:
parse_expr.c (r1.248 -> r1.249)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.248&r2=1.249)

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


[COMMITTERS] pgsql: When you do "ARRAY[...]::domain", where domain is a domain over

2009-11-13 Thread Heikki Linnakangas
Log Message:
---
When you do "ARRAY[...]::domain", where domain is a domain over an array type,
we need to check domain constraints. We used to do it correctly, but 8.4
introduced a separate code path for the "ARRAY[]::arraytype" case to infer
the type of an empty ARRAY construct from the cast target, and forgot to take
domains into account.

Per report from Florian G. Pflug.

Tags:

REL8_4_STABLE

Modified Files:
--
pgsql/src/backend/parser:
parse_expr.c (r1.241.2.2 -> r1.241.2.3)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.241.2.2&r2=1.241.2.3)

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


[COMMITTERS] pg-migrator - pg_migrator: Re-recommend vacuumdb because we don't

2009-11-13 Thread User Bmomjian
Log Message:
---
Re-recommend vacuumdb because we don't transfer the fsm or vm files.

Modified Files:
--
pg_migrator/src:
pg_migrator.c (r1.67 -> r1.68)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/pg_migrator/src/pg_migrator.c?r1=1.67&r2=1.68)

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


[COMMITTERS] pg-migrator - pg_migrator: Re-recommend vacuumdb because we don't

2009-11-13 Thread User Bmomjian
Log Message:
---
Re-recommend vacuumdb because we don't transfer the fsm or vm files.

Modified Files:
--
pg_migrator:
INSTALL (r1.45 -> r1.46)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/pg_migrator/INSTALL?r1=1.45&r2=1.46)
TODO (r1.23 -> r1.24)

(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pg-migrator/pg_migrator/TODO?r1=1.23&r2=1.24)

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


[COMMITTERS] pgsql: A better fix for the "ARRAY[...]::domain" problem.

2009-11-13 Thread Heikki Linnakangas
Log Message:
---
A better fix for the "ARRAY[...]::domain" problem. The previous patch worked,
but the transformed ArrayExpr claimed to have a return type of "domain",
even though the domain constraint was only checked by the enclosing
CoerceToDomain node. With this fix, the ArrayExpr is correctly labeled with
the base type of the domain. Per gripe by Tom Lane.

Modified Files:
--
pgsql/src/backend/parser:
parse_expr.c (r1.249 -> r1.250)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.249&r2=1.250)

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


[COMMITTERS] pgsql: A better fix for the "ARRAY[...]::domain" problem.

2009-11-13 Thread Heikki Linnakangas
Log Message:
---
A better fix for the "ARRAY[...]::domain" problem. The previous patch worked,
but the transformed ArrayExpr claimed to have a return type of "domain",
even though the domain constraint was only checked by the enclosing
CoerceToDomain node. With this fix, the ArrayExpr is correctly labeled with
the base type of the domain. Per gripe by Tom Lane.

Tags:

REL8_4_STABLE

Modified Files:
--
pgsql/src/backend/parser:
parse_expr.c (r1.241.2.3 -> r1.241.2.4)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c?r1=1.241.2.3&r2=1.241.2.4)

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


[COMMITTERS] pgsql: Add control knobs for plpgsql's variable resolution behavior, and

2009-11-13 Thread Tom Lane
Log Message:
---
Add control knobs for plpgsql's variable resolution behavior, and make the
default be "throw error on conflict", as per discussions.  The GUC variable
is plpgsql.variable_conflict, with values "error", "use_variable",
"use_column".  The behavior can also be specified per-function by inserting
one of
#variable_conflict error
#variable_conflict use_variable
#variable_conflict use_column
at the start of the function body.

The 8.5 release notes will need to mention using "use_variable" to retain
backward-compatible behavior, although we should encourage people to migrate
to the much less mistake-prone "error" setting.

Update the plpgsql documentation to match this and other recent changes.

Modified Files:
--
pgsql/doc/src/sgml:
config.sgml (r1.232 -> r1.233)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml?r1=1.232&r2=1.233)
plpgsql.sgml (r1.146 -> r1.147)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/plpgsql.sgml?r1=1.146&r2=1.147)
pgsql/src/pl/plpgsql/src:
gram.y (r1.135 -> r1.136)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/gram.y?r1=1.135&r2=1.136)
pl_comp.c (r1.145 -> r1.146)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_comp.c?r1=1.145&r2=1.146)
pl_handler.c (r1.47 -> r1.48)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_handler.c?r1=1.47&r2=1.48)
pl_scanner.c (r1.1 -> r1.2)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/pl_scanner.c?r1=1.1&r2=1.2)
plpgsql.h (r1.124 -> r1.125)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpgsql/src/plpgsql.h?r1=1.124&r2=1.125)
pgsql/src/test/regress/expected:
plpgsql.out (r1.81 -> r1.82)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/plpgsql.out?r1=1.81&r2=1.82)
pgsql/src/test/regress/sql:
plpgsql.sql (r1.68 -> r1.69)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/sql/plpgsql.sql?r1=1.68&r2=1.69)

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


[COMMITTERS] pgsql: Avoid assuming that enum CreateStmtLikeOption is unsigned.

2009-11-13 Thread Tom Lane
Log Message:
---
Avoid assuming that enum CreateStmtLikeOption is unsigned.  Zdenek Kotala

Modified Files:
--
pgsql/src/include/nodes:
parsenodes.h (r1.413 -> r1.414)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/parsenodes.h?r1=1.413&r2=1.414)

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


[COMMITTERS] pgsql: Clean up a couple of bizarre code formatting choices in recent

2009-11-13 Thread Tom Lane
Log Message:
---
Clean up a couple of bizarre code formatting choices in recent CREATE LIKE 
patch.

Modified Files:
--
pgsql/src/backend/parser:
parse_utilcmd.c (r2.29 -> r2.30)

(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_utilcmd.c?r1=2.29&r2=2.30)

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