Re: Performance while loading data and indexing
От | Mario Weilguni |
---|---|
Тема | Re: Performance while loading data and indexing |
Дата | |
Msg-id | 4D618F6493CE064A844A5D496733D6670390D5@freedom.icomedias.com обсуждение исходный текст |
Ответ на | Performance while loading data and indexing ("Shridhar Daithankar" <shridhar_daithankar@persistent.co.in>) |
Ответы |
Re: Performance while loading data and indexing
|
Список | pgsql-hackers |
>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?
В списке pgsql-hackers по дате отправления: