Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1XF1jr-0004qx-QU for pgsql-sql@arkaria.postgresql.org; Wed, 06 Aug 2014 13:58:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1XF1jr-0007Bx-67 for pgsql-sql@arkaria.postgresql.org; Wed, 06 Aug 2014 13:58:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XF1jq-0007Br-Bu for pgsql-sql@postgresql.org; Wed, 06 Aug 2014 13:58:46 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1XF1jh-0001zk-Md for pgsql-sql@postgresql.org; Wed, 06 Aug 2014 13:58:45 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by gateway1.nyi.internal (Postfix) with ESMTP id 6857A21BD7 for ; Wed, 6 Aug 2014 09:58:28 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 06 Aug 2014 09:58:28 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=5NvIY3MjpLMNDub3rbTd3PG0+N0=; b=ZW7o3n4GwmARGov6fjUgE447Bqlw PzSug7XxHL3ZLjBcv/Hzq/SFGVchct7rTl76njL5K5e1QIyxWsSWBzDBo0zM0ZbJ n1bFnNX8PwDpknnrJR0WVjZKEu6f7WCxOMZjAFXpJj+DCDjGUKaqbMmfof8BV2kR J3SLWC8gCO9OV0U= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=5NvIY3MjpLMNDub3rbTd3P G0+N0=; b=nUCYEAREzanHTBe/WzyAlqHSYPfyTebgZA15XSewqmG9lSJ9Hu+0Hs 4PUOZVxxa/PhMrTKS8zuWBXiA9FDn2O/Z1TkrsPZ46kKiiWF8QvZeq6hQWPysS+L VODTpf12yoc8jKneKQ+Gh5w9ntJdALu77Y5EyxSrYsGiAozMd2Jjw= X-Sasl-enc: VIgTVtKWTtzW74zsVOBEoQAWW+krfQPRPWmaIv8NLEZ1 1407333508 Received: from panda.site (unknown [174.21.176.242]) by mail.messagingengine.com (Postfix) with ESMTPA id ECA1868021C; Wed, 6 Aug 2014 09:58:27 -0400 (EDT) Message-ID: <53E23483.4030906@aklaver.com> Date: Wed, 06 Aug 2014 06:58:27 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Marcin Krawczyk CC: "pgsql-sql@postgresql.org" Subject: Re: function call References: <53E0D58E.9040502@aklaver.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-sql Precedence: bulk Sender: pgsql-sql-owner@postgresql.org 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.klaver@aklaver.com -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql