Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.org (8.9.2/8.9.1) with ESMTP id WAA37480 for ; Tue, 9 Mar 1999 22:31:05 -0500 (EST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id VAA16912; Tue, 9 Mar 1999 21:30:40 -0600 (CST) Message-ID: <19990309213040.A16905@Denninger.Net> Date: Tue, 9 Mar 1999 21:30:40 -0600 From: Karl Denninger To: Jason Slagle , Tim Perdue Cc: "D'Arcy J.M. Cain" , pgsql-sql@hub.org Subject: Re: [SQL] Performance References: <005201be6aa3$f9b5b040$0b8c5aa5@timnt.weather.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jason Slagle on Tue, Mar 09, 1999 at 10:24:05PM -0500 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Build appropriate indices for the fields you intend to discriminate on during a SELECT. 200MB is SMALL. I used to run searches over 10G of data in under 2 minutes looking for RADIUS detail records. The trick is to build the right set of indices for what you intend to be querying on. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. > What, if anything, are you using as an index. > > I have 1,400,000 entries (200MB) I'm inserting into a database. Radius > detail files as a matter of fact. Apart from COPY taking forever to load > that (probably due to my several indexes), it seems the select is VERY > slow. Any tips? > > How CPU intensive is a select? > > Jason > > --- > Jason Slagle > Network Administrator - Toledo Internet Access - Toledo Ohio > - raistlin@tacorp.net - jslagle@toledolink.com - WHOIS JS10172 > > On Tue, 9 Mar 1999, Tim Perdue wrote: > > > It searches the bodies, not the subjects or authors. I don't see why anyone > > needs to search for a particular author. But if it's requested enough, it > > would be trivial to implement..... > > > > Tim > > > > > > -----Original Message----- > > From: D'Arcy J.M. Cain > > To: perdue@raccoon.com > > Cc: pgsql-sql@hub.org > > Date: Tuesday, March 09, 1999 9:10 PM > > Subject: Re: [SQL] Performance > > > > > > >Thus spake Tim Perdue > > >> Some time back I sent out a message asking if PGSQL would be able to > > handle > > >> my mailing list archive at http://www.geocrawler.com/ , and whether it > > would > > >> scale up to 100MB. > > > > > >Cool. We now have a searchable archive for PostgreSQL. However, I > > >tried a search and it didn't seem to work. In pgsql-hackers I entered > > >"niladic" (I tried "Niladic" just in case) and it failed to find any > > >messages, even though I could see a few on the list of recent messages. > > >Any ideas? > > > > > >-- > > >D'Arcy J.M. Cain | Democracy is three wolves > > >http://www.druid.net/darcy/ | and a sheep voting on > > >+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner. > > > > > >