From: | Marcin Krawczyk <jankes(dot)mk(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: function call |
Date: | 2014-08-11 09:50:19 |
Message-ID: | CABnqL33m+KqSYqMW=YCHWSt3213CXoaS-8=tbkGuk=JibURd4w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
I've managed to determine that there's a trigger dependency tree that slows
things down. When I DISABLE one of them the function takes under 30
seconds, still more than from pgAdmin but much quicker than before.
regards
mk
2014-08-06 15:58 GMT+02:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>:
> On 08/06/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.
>>
>
> So it would seem that the issue is with ERP application returning the
> information.
>
> This probably hinges on what you are defining as returning?
>
> In your function description you note that the function issues documents.
>
> Is that what you are using to determine that the function has completed?
>
> If so, do you return the documents in the pgAdmin case as well?
>
> If not, how are measuring success(returning) in the application case?
>
>
>
>>
>> regards
>> mk
>>
>>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marcin Krawczyk | 2014-08-11 11:13:20 | Re: function call |
Previous Message | David G Johnston | 2014-08-10 18:10:54 | Re: Update Returning as subquery |