From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Unique Index Disk Consumption
Date: Wed, 27 Mar 2019 08:59:54 -0500
Message-ID: <9008124b-a440-9419-1a0f-fffd711fe476@gmail.com> (raw)
In-Reply-To: <PN1PR01MB08136DF37398A54E757D73A8AD580@PN1PR01MB0813.INDPRD01.PROD.OUTLOOK.COM>
References: <PN1PR01MB08136DF37398A54E757D73A8AD580@PN1PR01MB0813.INDPRD01.PROD.OUTLOOK.COM>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Unique Index Disk Consumption
In-Reply-To: <9008124b-a440-9419-1a0f-fffd711fe476@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox