Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 079349FBA3A for ; Mon, 23 Apr 2007 21:56:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 71511-02 for ; Mon, 23 Apr 2007 21:56:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from rrr3-v2.mail.re4.yahoo.com (rrr3-v2.mail.re4.yahoo.com [216.39.53.207]) by postgresql.org (Postfix) with SMTP id 423F99FBA0E for ; Mon, 23 Apr 2007 21:56:21 -0300 (ADT) Received: (qmail 73194 invoked from network); 24 Apr 2007 00:56:19 -0000 Received: from web54314.mail.yahoo.com (206.190.49.124) by rrr3-v2.mail.re4.yahoo.com with SMTP; 24 Apr 2007 00:56:19 -0000 Received: (qmail 9344 invoked by uid 60001); 24 Apr 2007 00:56:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=UMWgCxPiIYssDbj4rF5MuI7MIZFp6rUsDa5fuFRgPPSsjQp9xqm3dma+XNXXCCxXdFfYga1Wwwn1rQZY6bW7/sJ1CX9SD5kC/MDvwKhbxj6bsrWe4vdkg0WoNEYeKQ6+VftFNQs87smxZ88ReevBKJlZA3XYi/Hlfox+4l0/s4k=; X-YMail-OSG: AvFHkl4VM1lNTWAVSPXJ8M4lqwxostH2Xvbi6ZC3HmvvA7XuvQcOrrg48zyTEtbEOL7nIqUmwCsqC9TpaKp3xiPRyx6iaWGWBa6TlJdRiu9PsLsxQdC4aHyzFJG42S5P Received: from [24.2.63.115] by web54314.mail.yahoo.com via HTTP; Mon, 23 Apr 2007 17:56:19 PDT Date: Mon, 23 Apr 2007 17:56:19 -0700 (PDT) From: chester c young Subject: Re: Large journal as psql table. Good idea? Triggering. To: Bryce Nesbitt Cc: pgsql-sql@postgresql.org In-Reply-To: <462D3D4D.6090308@obviously.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <448237.8848.qm@web54314.mail.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/220 X-Sequence-Number: 28220 > But I'm thinking that maybe it's a job for a database table. Each > new > row would be written with a status (10="new"). And that the modem > process would poll for new rows. Problem is there will be lots of > rows, > but only a trivial few will be "new". The huge index file and the > polling seem like a drag on the database, unless there is a way to > optimize. create index on ( ) where status = 'new'; this index will be very fast. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com