[COMMITTERS] reorg - pg_reorg: Fix two bugs.

2010-04-21 Thread User Itagaki
Log Message: --- Fix two bugs. #1010789 : pg_reorg 1.1.0 and "unexpected toast relations" #1010790 : reorg.get_index_keys() does not handle composite indexes Modified Files: -- pg_reorg/bin: pg_reorg.c (r1.12 -> r1.13) (http://cvs.pgfoundry.org/cgi-bin/cvsw

[COMMITTERS] pgbouncer - pgbouncer: Make listen(2) backlog argument configurable.

2010-04-21 Thread User Mkz
Log Message: --- Make listen(2) backlog argument configurable. Modified Files: -- pgbouncer/doc: config.txt (r1.23 -> r1.24) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgbouncer/pgbouncer/doc/config.txt?r1=1.23&r2=1.24) pgbouncer/etc: pgbounce

[COMMITTERS] pgsql: Fix oversight in collecting values for cleanup_info records.

2010-04-21 Thread Simon Riggs
Log Message: --- Fix oversight in collecting values for cleanup_info records. vacuum_log_cleanup_info() now generates log records with a valid latestRemovedXid set in all cases. Also be careful not to zero the value when we do a round of vacuuming part-way through lazy_scan_heap(). Inciden

[COMMITTERS] pgsql: Relax locking during GetCurrentVirtualXIDs().

2010-04-21 Thread Simon Riggs
Log Message: --- Relax locking during GetCurrentVirtualXIDs(). Earlier improvements to handling of btree delete records mean that all snapshot conflicts on standby now have a valid, useful latestRemovedXid. Our earlier approach using LW_EXCLUSIVE was useful when we didnt always have a valid

[COMMITTERS] pgsql: Only send cleanup_info messages if VACUUM removes any tuples.

2010-04-21 Thread Simon Riggs
Log Message: --- Only send cleanup_info messages if VACUUM removes any tuples. There is no other purpose for this message type than to report the latestRemovedXid of removed tuples, prior to index scans. Removes overlooked path for sending invalid latestRemovedXid. Fixes buildfarm failure o

[COMMITTERS] pgsql: Enforce superuser permissions checks during ALTER ROLE/DATABASE

2010-04-21 Thread Tom Lane
Log Message: --- Enforce superuser permissions checks during ALTER ROLE/DATABASE SET, rather than during define_custom_variable(). This entails rejecting an ALTER command if the target variable doesn't have a known (non-placeholder) definition, unless the calling user is superuser. When t

Re: [COMMITTERS] pgsql: Only send cleanup_info messages if VACUUM removes any tuples.

2010-04-21 Thread Tom Lane
[email protected] (Simon Riggs) writes: > Removes overlooked path for sending invalid latestRemovedXid. > Fixes buildfarm failure on centaur. You're not there yet. There are multiple buildfarm machines showing TRAP: FailedAssertion("!(((vacrelstats->latestRemovedXid) != ((TransactionId) 0))

Re: [COMMITTERS] pgsql: Only send cleanup_info messages if VACUUM removes any tuples.

2010-04-21 Thread Simon Riggs
On Wed, 2010-04-21 at 21:03 -0400, Tom Lane wrote: > [email protected] (Simon Riggs) writes: > > Removes overlooked path for sending invalid latestRemovedXid. > > Fixes buildfarm failure on centaur. > > You're not there yet. There are multiple buildfarm machines showing > > TRAP: FailedAsser

[COMMITTERS] reorg - pg_batch: New Directory

2010-04-21 Thread User Itagaki
Update of /cvsroot/reorg/pg_batch/SPEC In directory pgfoundry.org:/tmp/cvs-serv40143/SPEC Log Message: Directory /cvsroot/reorg/pg_batch/SPEC added to the repository -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.post

[COMMITTERS] reorg - pg_batch: pg_batch 1.2.1.

2010-04-21 Thread User Itagaki
Log Message: --- pg_batch 1.2.1. Modified Files: -- pg_batch/doc: pg_batch-ja.html (r1.1.1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/reorg/pg_batch/doc/pg_batch-ja.html?r1=1.1.1.1&r2=1.2) pg_batch/pgut: pgut.c (r1.1.1.1 -> r1.2)

[COMMITTERS] reorg - pg_reorg: New Directory

2010-04-21 Thread User Itagaki
Update of /cvsroot/reorg/pg_reorg/SPECS In directory pgfoundry.org:/tmp/cvs-serv40847/SPECS Log Message: Directory /cvsroot/reorg/pg_reorg/SPECS added to the repository -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.p

[COMMITTERS] reorg - pg_reorg: pg_reorg 1.1.1.

2010-04-21 Thread User Itagaki
Log Message: --- pg_reorg 1.1.1. Added Files: --- pg_reorg/SPECS: pg_reorg.spec (r1.1) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/reorg/pg_reorg/SPECS/pg_reorg.spec?rev=1.1&content-type=text/x-cvsweb-markup) -- Sent via pgsql-committers mailing list (pgsql-

[COMMITTERS] pgsql: Fix encoding issue when lc_monetary or lc_numeric are different

2010-04-21 Thread Takahiro Itagaki
Log Message: --- Fix encoding issue when lc_monetary or lc_numeric are different encoding from lc_ctype, that could happen on Windows. We need to change lc_ctype together with lc_monetary or lc_numeric, and convert strings in lconv from lc_ctype encoding to the database encoding. The bug r

[COMMITTERS] pgsql: Further reductions in Hot Standby conflict processing.

2010-04-21 Thread Simon Riggs
Log Message: --- Further reductions in Hot Standby conflict processing. These come from the realistion that HEAP2_CLEAN records don't always remove user visible data, so conflict processing for them can be skipped. Confirm validity using Assert checks, clarify circumstances under which we l

[COMMITTERS] orafce - orafce: Adjust aggregate functions to PostgreSQL 9.0.

2010-04-21 Thread User Itagaki
Log Message: --- Adjust aggregate functions to PostgreSQL 9.0. Listagg functions are re-implemented with 9.0-based routines. Modified Files: -- orafce: aggregate.c (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/orafce/orafce/aggregate.c?r1=1.2&