Re: function call
| От | John L. Poole |
|---|---|
| Тема | Re: function call |
| Дата | |
| Msg-id | 53E219A9.10806@gmail.com обсуждение исходный текст |
| Ответ на | Re: function call (Marcin Krawczyk <jankes.mk@gmail.com>) |
| Список | pgsql-sql |
Wouldn't this issue be an excellent candidate to create a test example and then log a bug with all the details so others can recreate the issue? It's very difficult to divine what the problem is unless you can provide a working example that demonstrates it.
John
John
On 8/6/2014 12:41 AM, Marcin Krawczyk wrote:
It's not ODBC, I've just tested with simple C# through the same odbc source and the function takes 4 seconds as well.regards
mk2014-08-05 15:01 GMT+02:00 Adrian Klaver <adrian.klaver@aklaver.com>:On 08/05/2014 04:28 AM, Marcin Krawczyk wrote:Just had another thought.Hi list,
I have a SET returning function (defined as RETURNS TABLE), it takes 2
parameters and always returns one row with 3 columns. Now when I run it
from pgAdmin it takes around 5 seconds but when I run it from the
application its around 3 minutes (same parameters of course). It shows
up in the postgres' status server and odbc log right away so I believe
the applications has nothing to do with it. Where should I start looking ?
I found in the past that ODBC logging can slow things down considerably.
What happens if you turn off the ODBC logging?--
I'm running postgres 9.1
regards
mk
Adrian Klaver
adrian.klaver@aklaver.com
В списке pgsql-sql по дате отправления: