Received: from lists.unixathome.org (lists.unixathome.org [210.48.103.158]) by postgresql.org (Postfix) with ESMTP id 5A0BA4759A4 for ; Mon, 25 Feb 2002 00:31:00 -0500 (EST) Received: from wocker (lists.unixathome.org [210.48.103.158]) by lists.unixathome.org (8.11.6/8.11.6) with ESMTP id g1P5V3k60758 for ; Mon, 25 Feb 2002 18:31:03 +1300 (NZDT) (envelope-from dan@lists.unixathome.org) Message-Id: <200202250531.g1P5V3k60758@lists.unixathome.org> From: "Dan Langille" Organization: DVL Software Limited To: pgsql-sql@postgresql.org Date: Mon, 25 Feb 2002 00:30:59 -0500 MIME-Version: 1.0 Subject: processing faster with plpgsql by passing in more data Reply-To: dan@langille.org X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Archive-Number: 200202/350 X-Sequence-Number: 6772 The appliction involves passing a list of strings to the database and retrieving the results associated with those strings. If done one at a time, I can process about 6 or 7 strings a second. But I may have up to 300 or 400 strings. I don't want the user to sit around waiting that long and I'm looking for ways to speed this process up. At present, the user uploads a file to the webserver via each string is passed to the database one at a time and the result fetch back. I was thinking of passing in all the strings, getting the result set together and passing back all the results as a single result set, one for each string passed in. Comments? Ideas? cheers -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples