[COMMITTERS] npgsql - Npgsql2: Readded cast for byte[] when handling bytea

2008-04-11 Thread User Fxjr
Log Message: --- Readded cast for byte[] when handling bytea parameters which was removed by mistake. This was giving problems with byte[] support. Thanks Alaric for heads up. Modified Files: -- Npgsql2/src/Npgsql: NpgsqlCommand.cs (r1.20 -> r1.21) (htt

[COMMITTERS] pgsql: Fix main README typo.

2008-04-11 Thread Bruce Momjian
Log Message: --- Fix main README typo. Brendan Jurd Modified Files: -- pgsql: README (r1.34 -> r1.35) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/README?r1=1.34&r2=1.35) -- Sent via pgsql-committers mailing list ([email protected]) To ma

[COMMITTERS] pgsql: Update URLs for dead space map.

2008-04-11 Thread Bruce Momjian
Log Message: --- Update URLs for dead space map. Modified Files: -- pgsql/doc: TODO (r1.2411 -> r1.2412) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2411&r2=1.2412) pgsql/doc/src/FAQ: TODO.html (r1.917 -> r1.918) (http

[COMMITTERS] pgsql: Add TODO: > * Support procedures, which return no value > >

2008-04-11 Thread Bruce Momjian
Log Message: --- Add TODO: > * Support procedures, which return no value > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01375.php Modified Files: -- pgsql/doc: TODO (r1.2412 -> r1.2413) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TO

[COMMITTERS] pgsql: Changed TODO wording: < * Support procedures, which return no

2008-04-11 Thread Bruce Momjian
Log Message: --- Changed TODO wording: < * Support procedures, which return no value > * Allow functions to control the transaction state Modified Files: -- pgsql/doc: TODO (r1.2413 -> r1.2414) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.

Re: [COMMITTERS] pgsql: Changed TODO wording: < * Support procedures, which return no

2008-04-11 Thread Tom Lane
[EMAIL PROTECTED] (Bruce Momjian) writes: > Log Message: > --- > Changed TODO wording: > < * Support procedures, which return no value > > * Allow functions to control the transaction state I can't imagine that we'd implement this by "allowing functions to control the transaction state".

[COMMITTERS] pgsql: Update wording: < * Allow functions to control the transaction

2008-04-11 Thread Bruce Momjian
Log Message: --- Update wording: < * Allow functions to control the transaction state > * Allow calling of a procedure outside a SELECT that can control the > transaction state Modified Files: -- pgsql/doc: TODO (r1.2414 -> r1.2415) (http://anoncvs.postg

Re: [COMMITTERS] pgsql: Changed TODO wording: < * Support procedures, which return no

2008-04-11 Thread Bruce Momjian
Tom Lane wrote: > [EMAIL PROTECTED] (Bruce Momjian) writes: > > Log Message: > > --- > > Changed TODO wording: > > > < * Support procedures, which return no value > > > * Allow functions to control the transaction state > > I can't imagine that we'd implement this by "allowing functions t

[COMMITTERS] pgsql: Fix several datatype input functions that were allowing unused

2008-04-11 Thread Tom Lane
Log Message: --- Fix several datatype input functions that were allowing unused bytes in their results to contain uninitialized, unpredictable values. While this was okay as far as the datatypes themselves were concerned, it's a problem for the parser because occurrences of the "same" lite

[COMMITTERS] pgsql: Fix several datatype input functions that were allowing unused

2008-04-11 Thread Tom Lane
Log Message: --- Fix several datatype input functions that were allowing unused bytes in their results to contain uninitialized, unpredictable values. While this was okay as far as the datatypes themselves were concerned, it's a problem for the parser because occurrences of the "same" lite

[COMMITTERS] pgsql: Fix several datatype input functions that were allowing unused

2008-04-11 Thread Tom Lane
Log Message: --- Fix several datatype input functions that were allowing unused bytes in their results to contain uninitialized, unpredictable values. While this was okay as far as the datatypes themselves were concerned, it's a problem for the parser because occurrences of the "same" lite

[COMMITTERS] pgsql: Fix several datatype input functions that were allowing unused

2008-04-11 Thread Tom Lane
Log Message: --- Fix several datatype input functions that were allowing unused bytes in their results to contain uninitialized, unpredictable values. While this was okay as far as the datatypes themselves were concerned, it's a problem for the parser because occurrences of the "same" lite

[COMMITTERS] pgsql: Fix several datatype input functions that were allowing unused

2008-04-11 Thread Tom Lane
Log Message: --- Fix several datatype input functions that were allowing unused bytes in their results to contain uninitialized, unpredictable values. While this was okay as far as the datatypes themselves were concerned, it's a problem for the parser because occurrences of the "same" lite

[COMMITTERS] pgsql: Fix several datatype input functions that were allowing unused

2008-04-11 Thread Tom Lane
Log Message: --- Fix several datatype input functions that were allowing unused bytes in their results to contain uninitialized, unpredictable values. While this was okay as far as the datatypes themselves were concerned, it's a problem for the parser because occurrences of the "same" lite

[COMMITTERS] pgsql: Add some debug support code to try to catch future mistakes in

2008-04-11 Thread Tom Lane
Log Message: --- Add some debug support code to try to catch future mistakes in the area of input functions that include garbage bytes in their results. Provide a compile-time option RANDOMIZE_ALLOCATED_MEMORY to make palloc fill returned blocks with variable contents. This option also ma

[COMMITTERS] pgsql: A quick try at un-breaking the Cygwin build.

2008-04-11 Thread Tom Lane
Log Message: --- A quick try at un-breaking the Cygwin build. Whether it needs the pgwin32_safestat remains to be determined, but in any case the current code is not tolerable. Modified Files: -- pgsql/src/include: port.h (r1.119 -> r1.120) (http://anoncvs

[COMMITTERS] pgsql: A quick try at un-breaking the Cygwin build.

2008-04-11 Thread Tom Lane
Log Message: --- A quick try at un-breaking the Cygwin build. Whether it needs the pgwin32_safestat remains to be determined, but in any case the current code is not tolerable. Tags: REL8_3_STABLE Modified Files: -- pgsql/src/include: port.h (r1.116.2.2 -> r1

[COMMITTERS] pgsql: A quick try at un-breaking the Cygwin build.

2008-04-11 Thread Tom Lane
Log Message: --- A quick try at un-breaking the Cygwin build. Whether it needs the pgwin32_safestat remains to be determined, but in any case the current code is not tolerable. Tags: REL8_2_STABLE Modified Files: -- pgsql/src/include: port.h (r1.106.2.4 -> r1