[COMMITTERS] npgsql - Npgsql2: Fixed tabulation.

2012-01-09 Thread User Fxjr
Log Message: --- Fixed tabulation. Modified Files: -- Npgsql2/src/Npgsql: NpgsqlConnectorPool.cs (r1.20 -> r1.21) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlConnectorPool.cs?r1=1.20&r2=1.21) -- Sent via pgsql-committers

[COMMITTERS] pgsql: Fix one-byte buffer overrun in contrib/test_parser.

2012-01-09 Thread Tom Lane
Fix one-byte buffer overrun in contrib/test_parser. The original coding examined the next character before verifying that there *is* a next character. In the worst case with the input buffer right up against the end of memory, this would result in a segfault. Problem spotted by Paul Guyot; this

[COMMITTERS] pgsql: Fix one-byte buffer overrun in contrib/test_parser.

2012-01-09 Thread Tom Lane
Fix one-byte buffer overrun in contrib/test_parser. The original coding examined the next character before verifying that there *is* a next character. In the worst case with the input buffer right up against the end of memory, this would result in a segfault. Problem spotted by Paul Guyot; this

[COMMITTERS] pgsql: Fix one-byte buffer overrun in contrib/test_parser.

2012-01-09 Thread Tom Lane
Fix one-byte buffer overrun in contrib/test_parser. The original coding examined the next character before verifying that there *is* a next character. In the worst case with the input buffer right up against the end of memory, this would result in a segfault. Problem spotted by Paul Guyot; this

[COMMITTERS] pgsql: Fix one-byte buffer overrun in contrib/test_parser.

2012-01-09 Thread Tom Lane
Fix one-byte buffer overrun in contrib/test_parser. The original coding examined the next character before verifying that there *is* a next character. In the worst case with the input buffer right up against the end of memory, this would result in a segfault. Problem spotted by Paul Guyot; this

[COMMITTERS] pgsql: Fix one-byte buffer overrun in contrib/test_parser.

2012-01-09 Thread Tom Lane
Fix one-byte buffer overrun in contrib/test_parser. The original coding examined the next character before verifying that there *is* a next character. In the worst case with the input buffer right up against the end of memory, this would result in a segfault. Problem spotted by Paul Guyot; this

[COMMITTERS] pgsql: Add compatibility note about grant options on GRANT reference pa

2012-01-09 Thread Peter Eisentraut
Add compatibility note about grant options on GRANT reference page Point out in the compatibility section that granting grant options to PUBLIC is not supported by PostgreSQL. This is already mentioned earlier, but since it concerns the information schema, it might be worth pointing out explicitl

[COMMITTERS] pgsql: Fix pathname in pgindent README.

2012-01-09 Thread Robert Haas
Fix pathname in pgindent README. Kevin Grittner Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/dc3f33f6be0be3f7ce25511d4485506ec43e20aa Modified Files -- src/tools/pgindent/README |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) -- Sent via

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Peter Eisentraut
On mån, 2012-01-09 at 17:06 +, Dave Page wrote: > Is there a way I can get gcc to spit out the expanded definition in a > readable format that you know of? make plpy_cursorobject.i -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscript

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Andrew Dunstan
On 01/09/2012 12:13 PM, Peter Geoghegan wrote: On 9 January 2012 17:06, Dave Page wrote: Is there a way I can get gcc to spit out the expanded definition in a readable format that you know of? Yes. Figure out what flags gcc is given when building the TU. Then, add the -E flag and see what is

[COMMITTERS] pgsql: Add .gitignore file for entab

2012-01-09 Thread Magnus Hagander
Add .gitignore file for entab Kevin Grittner Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/822128947eb707830ad1b775c216517c3a54befc Modified Files -- src/tools/entab/.gitignore |1 + 1 files changed, 1 insertions(+), 0 deletions(-) -- Sent via pg

[COMMITTERS] pgsql: Fix comment language

2012-01-09 Thread Magnus Hagander
Fix comment language Per comment from Heikki Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4ecd359c420203082489e2b5098e34a1b70c Modified Files -- src/bin/pg_basebackup/receivelog.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) --

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Peter Geoghegan
On 9 January 2012 17:06, Dave Page wrote: > Is there a way I can get gcc to spit out the expanded definition in a > readable format that you know of? Yes. Figure out what flags gcc is given when building the TU. Then, add the -E flag and see what is generated: http://www.network-theory.co.uk/doc

[COMMITTERS] pgsql: Fix pg_basebackup for keepalive messages

2012-01-09 Thread Magnus Hagander
Fix pg_basebackup for keepalive messages Teach pg_basebackup in streaming mode to deal with keepalive messages. Also change the order of checks to complain at the message rather than block size when a new message is introduced. In passing, switch to using sizeof() instead of hardcoded sizes for W

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Dave Page
On Mon, Jan 9, 2012 at 4:57 PM, Tom Lane wrote: > Andrew Dunstan writes: >> On 01/09/2012 10:52 AM, Dave Page wrote: >>> Yes, it's defined as such: >>> PyAPI_FUNC(PyObject *) PyObject_SelfIter(PyObject *); > >> Hmm. Well, at this stage I'm slightly inclined to say it's a compiler >> problem. That

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Tom Lane
Andrew Dunstan writes: > On 01/09/2012 10:52 AM, Dave Page wrote: >> Yes, it's defined as such: >> PyAPI_FUNC(PyObject *) PyObject_SelfIter(PyObject *); > Hmm. Well, at this stage I'm slightly inclined to say it's a compiler > problem. That's a pretty old compiler. If you can't upgrade it maybe

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Andrew Dunstan
On 01/09/2012 10:52 AM, Dave Page wrote: On Mon, Jan 9, 2012 at 3:35 PM, Andrew Dunstan wrote: On 12/14/2011 06:43 PM, Jan Urbański wrote: - Original message - On 12/05/2011 12:56 PM, Peter Eisentraut wrote: plpython: Add SPI cursor support Add a function plpy.cursor that is sim

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Dave Page
On Mon, Jan 9, 2012 at 3:35 PM, Andrew Dunstan wrote: > > > > On 12/14/2011 06:43 PM, Jan Urbański wrote: >> >> - Original message - >>> >>> On 12/05/2011 12:56 PM, Peter Eisentraut wrote: plpython: Add SPI cursor support Add a function plpy.cursor that is similar to pl

Re: [COMMITTERS] pgsql: plpython: Add SPI cursor support

2012-01-09 Thread Andrew Dunstan
On 12/14/2011 06:43 PM, Jan Urbański wrote: - Original message - On 12/05/2011 12:56 PM, Peter Eisentraut wrote: plpython: Add SPI cursor support Add a function plpy.cursor that is similar to plpy.execute but uses an SPI cursor to avoid fetching the entire result set into memory. Ja

[COMMITTERS] npgsql - Npgsql2: Fix [#1011138] Connection pooling performance suffers

2012-01-09 Thread User Fxjr
Log Message: --- Fix [#1011138] Connection pooling performance suffers under heavy load. Rewritten connector pool logic in order to keep lock for much less time and also with a higher granularity. Thanks Andrew for heads up. Modified Files: -- Npgsql2/src/Npgsql: