Skip site navigation (1) Skip section navigation (2)

Re: Performance while loading data and indexing

From: "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in>
To: "Mario Weilguni" <mario(dot)weilguni(at)icomedias(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Performance while loading data and indexing
Date: 2002-09-26 09:58:01
Message-ID: 3D932781.14221.1386312B@localhost (view raw or flat)
Thread:
Lists: pgsql-hackers
On 26 Sep 2002 at 11:50, Mario Weilguni wrote:

> >Well the test runs were for 10GB of data. Schema is attached. Read in fixed 
> >fonts..Last nullable fields are dummies but may be used in fututre and
> varchars 
> >are not acceptable(Not my requirement). Tuple size is around 100 bytes..
> >The index creation query was
> >
> >CREATE INDEX index1 ON tablename (esn,min,datetime);
> >
> >What if I put datetime ahead? It's likely the the datetime field will have
> high 
> >degree of locality being log data..
> 
> Just an idea, I noticed you use char(10) for esn and min, and use this as
> index. Are these really fixed len fields all having 10 bytes? Otherwise
> varchar(10) would be better, because your tables, and especially the indices
> will be probably much smaller.
> 
> what average length do you have for min and esn?

10 bytes. Those are id numbers.. like phone numbers always have all the digits 
filled in..



Bye
 Shridhar

--
Bradley's Bromide:	If computers get too powerful, we can organize	them into a 
committee -- that will do them in.


In response to

Responses

pgsql-hackers by date

Next:From: Tim KnowlesDate: 2002-09-26 10:20:40
Subject: 7.3b1 : DROP DOMAIN CASCADE CAN LEAVE A TABLE WITH NO COLUMNS
Previous:From: Justin CliftDate: 2002-09-26 09:56:34
Subject: Re: [HACKERS] Performance while loading data and indexing

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group