From: | Евгений Селявка <evg(dot)selyavka(at)gmail(dot)com> |
---|---|
To: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | estimate btree index size without creating |
Date: | 2014-07-22 07:38:18 |
Message-ID: | CAKPhvNaqxycnwDh+cq1mkKAEvNCeNOZRxq1+Qz5ty-_cSECJYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Dear all,
Is it possible to estimate btree index size on text field before
creating it. For example i have a table like this:
fortest=# \d index_estimate
i integer
somestring text
This is avg bytes in text field
fortest=# select round(avg(octet_length(somestring))) from index_estimate ;
4
And number of tuples is
fortest=# select reltuples from pg_class where relname = 'index_estimate';
10001
Can i estimate index size, operate only this data, may be exist
formula or something to do this estimation.
--
Best Regards,
Seliavka Evgenii
From | Date | Subject | |
---|---|---|---|
Next Message | johno | 2014-07-22 10:42:26 | Re: Slow query with indexed ORDER BY and LIMIT when using OR'd conditions |
Previous Message | Tom Lane | 2014-07-22 06:15:29 | Re: Slow query with indexed ORDER BY and LIMIT when using OR'd conditions |