X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id B72DAD1B520 for ; Tue, 9 Sep 2003 13:28:23 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 95539-08 for ; Tue, 9 Sep 2003 10:27:56 -0300 (ADT) Received: from mailav.tor1.inquent.com (mail.inquent.com [216.208.117.106]) by svr1.postgresql.org (Postfix) with ESMTP id A2A0FD1B4F6 for ; Tue, 9 Sep 2003 10:27:52 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by mailav.tor1.inquent.com (Postfix) with ESMTP id 7EC5B1025C; Tue, 9 Sep 2003 09:19:25 -0400 (EDT) Received: from [10.0.2.8] (unknown [10.0.2.8]) by mailav.tor1.inquent.com (Postfix) with ESMTP id A6BE010248; Tue, 9 Sep 2003 09:19:23 -0400 (EDT) Subject: Re: Need advice about triggers From: Rod Taylor To: Mindaugas Riauba Cc: Postgresql Performance In-Reply-To: <00be01c376cf$91510620$f20214ac@bite.lt> References: <00be01c376cf$91510620$f20214ac@bite.lt> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-oEpXWNR807newZCxoHgv" Message-Id: <1063114086.67981.5.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Tue, 09 Sep 2003 09:28:07 -0400 X-Virus-Scanned: by AMaViS perl-11 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/148 X-Sequence-Number: 3514 --=-oEpXWNR807newZCxoHgv Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > How can I improve performance and will version 7.4 bring something > valuable for my task? Rewrite to some other scripting language is not > a problem. Trigger is simple enough. Your best bet is to have additional clients connected to the database requesting work. Approx NUMCPUs * 2 + 1 seems to be ideal. (+1 to ensure there is something waiting when the others complete. *2 to ensure that you can have 50% reading from disk, 50% doing calculations) You may simply want to put vacuum into a loop of it's own so it executes ~1 second after the previous run finished. Work should still be going on even though vacuum is running. --=-oEpXWNR807newZCxoHgv Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/XdVm6DETLow6vwwRAtoeAJ4kZ2d1jzJG5NMstnxZdMnDQcgOOQCcCbw6 fzObcMoxLLgG9YBe2skRwfg= =ffrR -----END PGP SIGNATURE----- --=-oEpXWNR807newZCxoHgv--