Log Message:
---
Fix some comments typo and Add some comments.
Modified Files:
--
pg_statsinfo:
COPYRIGHT (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgstatsinfo/pg_statsinfo/COPYRIGHT?r1=1.1&r2=1.2)
pg_statsinfo/bin:
collector.c
Add maintainer-check target
This can do various source code checks that are not appropriate for
either the build or the regression tests. Currently: duplicate_oids,
SGML syntax and tabs check, NLS syntax check.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/6c0dfc0
Make duplicate_oids return nonzero exit status if duplicates were found
Automatic detection of errors is easier that way.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/aa6fdd186cf2c29e04d3cc8ca19783fb904a5a33
Modified Files
--
src/include/catalog/dupli
Prevent a rowtype from being included in itself.
Eventually we might be able to allow that, but it's not clear how many
places need to be fixed to prevent infinite recursion when there's a direct
or indirect inclusion of a rowtype in itself. One such place is
CheckAttributeType(), which will recu
Prevent a rowtype from being included in itself.
Eventually we might be able to allow that, but it's not clear how many
places need to be fixed to prevent infinite recursion when there's a direct
or indirect inclusion of a rowtype in itself. One such place is
CheckAttributeType(), which will recu
Prevent a rowtype from being included in itself.
Eventually we might be able to allow that, but it's not clear how many
places need to be fixed to prevent infinite recursion when there's a direct
or indirect inclusion of a rowtype in itself. One such place is
CheckAttributeType(), which will recu
Prevent a rowtype from being included in itself.
Eventually we might be able to allow that, but it's not clear how many
places need to be fixed to prevent infinite recursion when there's a direct
or indirect inclusion of a rowtype in itself. One such place is
CheckAttributeType(), which will recu
Add 9.1 release note link for synchronous replication.
We already had links to the GUC variables that control it.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5c22c0eda14594b5962aed7165a012067b33ab7d
Modified Files
--
doc/src/sgml/release-9.1.sgml |
Tag refs/tags/REL9_1_ALPHA5 was created.
--
Sent via pgsql-committers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
Mark up release notes using .
Unlike , this actually works.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/7c7fd882a5275bf40cd5ac72c6118916f7802aa4
Modified Files
--
doc/src/sgml/release-9.1.sgml | 17 +
1 files changed, 9 insertions(+)
Add missing #include
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/e5948e3504c72fb2b8b32af26bfbb016e7c71bf6
Modified Files
--
contrib/sepgsql/sepgsql.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
--
Sent via pgsql-committers mailing li
Get rid of links that don't work when building HISTORY.
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/a720c28f0af3185f7d40788a78867a36bff36bc7
Modified Files
--
doc/src/sgml/release-9.1.sgml | 18 +-
1 files changed, 9 insertions(+), 9
Heikki Linnakangas writes:
> On 27.03.2011 19:51, Tom Lane wrote:
>> Fix plpgsql to release SPI plans when a function or DO block is freed.
> I was quite surprised by the way you did this. Instead of adding all
> that code to traverse the PLpgSQL_stmt tree (that we'll have to remember
> to keep
On 27.03.2011 19:51, Tom Lane wrote:
Fix plpgsql to release SPI plans when a function or DO block is freed.
This fixes the gripe I made a few months ago about DO blocks getting
slower with repeated use. At least, it fixes it for the case where
the DO block isn't aborted by an error. We could t
14 matches
Mail list logo
