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

From: fxjr(at)pgfoundry(dot)org (User Fxjr)
To: pgsql-committers(at)postgresql(dot)org
Subject: npgsql - Npgsql2: [#1010495] Bad performance calling a (empty) function
Date: 2008-11-11 17:58:33
Message-ID: 20081111175834.02D0A17AD9D8@pgfoundry.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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 more than 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-11-11 18:13:32 pgsql: Get rid of adjust_appendrel_attr_needed(), which has been broken
Previous Message User Fxjr 2008-11-11 16:58:22 npgsql - Npgsql2: Fixed a typo which prevented DateTime.MaxValue to