Re: Performance while loading data and indexing - Mailing list pgsql-hackers

From Shridhar Daithankar
Subject Re: Performance while loading data and indexing
Date
Msg-id 3D932781.14221.1386312B@localhost
Whole thread Raw
In response to Re: Performance while loading data and indexing  ("Mario Weilguni" <mario.weilguni@icomedias.com>)
Responses Re: Performance while loading data and indexing
List 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..



ByeShridhar

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



pgsql-hackers by date:

Previous
From: Justin Clift
Date:
Subject: Re: [GENERAL] Performance while loading data and indexing
Next
From: "Tim Knowles"
Date:
Subject: 7.3b1 : DROP DOMAIN CASCADE CAN LEAVE A TABLE WITH NO COLUMNS