Log Message:
---
Add support for PostgreSQL 8.5's INLINE functions
Modified Files:
--
pllolcode:
DOC (r1.32 -> r1.33)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pllolcode/pllolcode/DOC?r1=1.32&r2=1.33)
pllolcode.c (r1.32 -> r1.33)
(http:/
Log Message:
---
Build bzip2 tarball in dist target as well
Modified Files:
--
pgsql:
GNUmakefile.in (r1.54 -> r1.55)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/GNUmakefile.in?r1=1.54&r2=1.55)
pgsql/src:
Makefile.global.in (r1.258 -> r1.259
Log Message:
---
Fix regression tests for psql \d view patch
Modified Files:
--
pgsql/src/test/regress/expected:
polymorphism.out (r1.21 -> r1.22)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/polymorphism.out?r1=1.21&r2=1.22)
[email protected] (Peter Eisentraut) writes:
> In psql, show view definition only with \d+, not with \d
This broke the regression tests.
regards, tom lane
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription
Log Message:
---
Improve PL/Python elog output
When the elog functions (plpy.info etc.) get a single argument, just print
that argument instead of printing the single-member tuple like ('foo',).
Modified Files:
--
pgsql/src/pl/plpython:
plpython.c (r1.131 -> r1.132
Log Message:
---
In psql, show view definition only with \d+, not with \d
The rationale is that view definitions tend to be long and obscure the
main information about the view.
Modified Files:
--
pgsql/src/bin/psql:
describe.c (r1.229 -> r1.230)
(http://a
Log Message:
---
Fix obscure segfault condition in PL/Python
In PLy_output(), when the elog() call in the TRY branch throws an exception
(this can happen when a statement timeout kicks in, for example), the
PyErr_SetString() call in the CATCH branch can cause a segfault, because the
Py_XDE
Log Message:
---
Fix obscure segfault condition in PL/Python
In PLy_output(), when the elog() call in the TRY branch throws an exception
(this can happen when a statement timeout kicks in, for example), the
PyErr_SetString() call in the CATCH branch can cause a segfault, because the
Py_XDE
Log Message:
---
Fix obscure segfault condition in PL/Python
In PLy_output(), when the elog() call in the TRY branch throws an exception
(this can happen when a statement timeout kicks in, for example), the
PyErr_SetString() call in the CATCH branch can cause a segfault, because the
Py_XDE
Log Message:
---
Fix obscure segfault condition in PL/Python
In PLy_output(), when the elog() call in the TRY branch throws an exception
(this can happen when a statement timeout kicks in, for example), the
PyErr_SetString() call in the CATCH branch can cause a segfault, because the
Py_XDE
Log Message:
---
Fix obscure segfault condition in PL/Python
In PLy_output(), when the elog() call in the TRY branch throws an exception
(this can happen when a statement timeout kicks in, for example), the
PyErr_SetString() call in the CATCH branch can cause a segfault, because the
Py_XDE
11 matches
Mail list logo
