npgsql - Npgsql2: [#1010495] Bad performance calling a (empty) function - Mailing list pgsql-committers

From fxjr@pgfoundry.org (User Fxjr)
Subject npgsql - Npgsql2: [#1010495] Bad performance calling a (empty) function
Date
Msg-id 20081111175834.02D0A17AD9D8@pgfoundry.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------

[#1010495] Bad performance calling a (empty) function very often.
Now NpgsqlCommand caches previous results of internal checkings which were taking too much time if the command was used
morethan once. 

Modified Files:
--------------
    Npgsql2/src/Npgsql:
        NpgsqlCommand.cs (r1.30 -> r1.31)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/npgsql/Npgsql2/src/Npgsql/NpgsqlCommand.cs.diff?r1=1.30&r2=1.31)

pgsql-committers by date:

Previous
From: fxjr@pgfoundry.org (User Fxjr)
Date:
Subject: npgsql - Npgsql2: Fixed a typo which prevented DateTime.MaxValue to
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Get rid of adjust_appendrel_attr_needed(), which has been broken