X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id A9DCB9FB224 for ; Thu, 24 Aug 2006 10:02:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 53518-06 for ; Thu, 24 Aug 2006 13:02:15 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web50303.mail.yahoo.com (web50303.mail.yahoo.com [206.190.38.57]) by postgresql.org (Postfix) with SMTP id 2233E9FB1CA for ; Thu, 24 Aug 2006 10:02:14 -0300 (ADT) Received: (qmail 47859 invoked by uid 60001); 24 Aug 2006 13:02:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=desEieVpLytt2pqknVI7Ik03t6d62BDAhB5DtCnG1eR10vXgSt7AczKK/8w8/uUfg3EZCdVuMMtuffN7YWVj0xqYtsWntaqQf+aUd2jLwshrHctekkqNTuNjGtkQL/veg+bQbwCaQZE/4Efcu8sY4ijylAWc8cvrYXU3YqE+eUs= ; Message-ID: <20060824130209.47857.qmail@web50303.mail.yahoo.com> Received: from [193.163.1.105] by web50303.mail.yahoo.com via HTTP; Thu, 24 Aug 2006 06:02:08 PDT Date: Thu, 24 Aug 2006 06:02:08 -0700 (PDT) From: Thor Tall Subject: Re: Slow delete/insert. To: Alexandre Leclerc Cc: pgsql-admin@postgresql.org In-Reply-To: <1dc7f0e30608240508t49a208acnbe26769e1b6f669d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.816 tagged_above=0 required=5 tests=SPF_HELO_SOFTFAIL, SPF_SOFTFAIL X-Spam-Level: *** X-Archive-Number: 200608/263 X-Sequence-Number: 22806 The messages are split on the client side and PQexec are called with INSERT/DELETE statements. I have seen that I could use PQprepare and PQexecPrepared but I doubt that it would help a lot to use those functions? /Thor --- Alexandre Leclerc wrote: > All this is prety straight forward. > > As for the transaction you are crating, is the > process of 'split > message' actually do on the DB side or are you doing > this process on > you side? Maybe this is the actual work of splitting > the message by > the DB that is very slow. > > /Maybe/ if you do this data-processing on your side, > then sending that > to the DB will save you time. If you really want > that job being done > on the server side, you could build yourself an > extension module > adding a special function that you would call to do > the job. Maybe you > could win couple cycles... > > But all that could be confirmed or not by someone > else which knows > more about PG internals. > > Best regards. > > -- > Alexandre Leclerc > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com