[COMMITTERS] pgsql: Update docs about new role privileges reference, per Alvaro.

2011-02-21 Thread Bruce Momjian
Update docs about new role privileges reference, per Alvaro. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/ede45e90dd1992bfd3e1e61ce87bad494b81f54d Modified Files -- doc/src/sgml/user-manag.sgml |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(

[COMMITTERS] pgsql: Move information_schema duplicate constraint note to the top of

2011-02-21 Thread Bruce Momjian
Move information_schema duplicate constraint note to the top of the information schema documentation because it affects several tables. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/fee7802770669398359c369aee83277dcc58edd1 Modified Files -- doc/src/sgml

[COMMITTERS] npgsql - Npgsql2: Exception when closing connection.

2011-02-21 Thread User Fxjr
Log Message: --- Exception when closing connection. If your connection is in the Ready state and the stream is actually broken NpgsqlReadyState.Close will throw an exception when trying to write to the stream. More info can be found at: http://pgfoundry.org/forum/forum.php?thread_id=100

[COMMITTERS] npgsql - Npgsql2: NpgsqlConnector.CancelRequest leaks Connector.

2011-02-21 Thread User Fxjr
Log Message: --- NpgsqlConnector.CancelRequest leaks Connector. NpgsqlConnector.CancelRequest creates a connector to cancel the running request, but does not close it. More info at: http://pgfoundry.org/forum/forum.php?thread_id=10059&forum_id=519 Thanks David Leaver for patch. Modifie

[COMMITTERS] pgsql: Fix dangling-pointer problem in before-row update trigger proces

2011-02-21 Thread Tom Lane
Fix dangling-pointer problem in before-row update trigger processing. ExecUpdate checked for whether ExecBRUpdateTriggers had returned a new tuple value by seeing if the returned tuple was pointer-equal to the old one. But the "old one" was in estate->es_junkFilter's result slot, which would be s

[COMMITTERS] pgsql: Fix dangling-pointer problem in before-row update trigger proces

2011-02-21 Thread Tom Lane
Fix dangling-pointer problem in before-row update trigger processing. ExecUpdate checked for whether ExecBRUpdateTriggers had returned a new tuple value by seeing if the returned tuple was pointer-equal to the old one. But the "old one" was in estate->es_junkFilter's result slot, which would be s

[COMMITTERS] pgsql: Fix dangling-pointer problem in before-row update trigger proces

2011-02-21 Thread Tom Lane
Fix dangling-pointer problem in before-row update trigger processing. ExecUpdate checked for whether ExecBRUpdateTriggers had returned a new tuple value by seeing if the returned tuple was pointer-equal to the old one. But the "old one" was in estate->es_junkFilter's result slot, which would be s

[COMMITTERS] pgsql: Fix dangling-pointer problem in before-row update trigger proces

2011-02-21 Thread Tom Lane
Fix dangling-pointer problem in before-row update trigger processing. ExecUpdate checked for whether ExecBRUpdateTriggers had returned a new tuple value by seeing if the returned tuple was pointer-equal to the old one. But the "old one" was in estate->es_junkFilter's result slot, which would be s

[COMMITTERS] pgsql: Fix dangling-pointer problem in before-row update trigger proces

2011-02-21 Thread Tom Lane
Fix dangling-pointer problem in before-row update trigger processing. ExecUpdate checked for whether ExecBRUpdateTriggers had returned a new tuple value by seeing if the returned tuple was pointer-equal to the old one. But the "old one" was in estate->es_junkFilter's result slot, which would be s

[COMMITTERS] pgsql: Remove ExecRemoveJunk(), which is no longer used anywhere.

2011-02-21 Thread Tom Lane
Remove ExecRemoveJunk(), which is no longer used anywhere. This was a leftover from the pre-8.1 design of junkfilters. It doesn't seem to have any reason to live, since it's merely a combination of two easy function calls, and not a well-designed combination at that (it encourages callers to leak