| From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Unique Index Disk Consumption |
| Date: | 2019-03-27 13:59:54 |
| Message-ID: | 9008124b-a440-9419-1a0f-fffd711fe476@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 3/27/19 8:50 AM, Moin Akther wrote:
> Dear Experts,
>
> on a table we have 2 unique index's and when i check the table and unique
> index size, size of index's are twice the size of table.
>
> if have drop both the unique index's and create the new one but again
> after some time index size is almost twice the size of table.
>
> Is Unique Index consume more disk space ?
How big is each row?
Are the rows compressible?
How big are PK fields?
>
> How can i manage this kind scenario ? as droping and recreating unique
> index on the existing data is taking lot of time.
Why do you *need* to?
--
Angular momentum makes the world go 'round.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith Fiske | 2019-03-27 14:25:34 | Re: Unique Index Disk Consumption |
| Previous Message | Moin Akther | 2019-03-27 13:50:54 | Unique Index Disk Consumption |