| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Voils, Steven M" <steve(at)sensorswitch(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Primary key vs unique index |
| Date: | 2011-03-17 18:51:45 |
| Message-ID: | AANLkTi=m9xtpihOYC9+EfGNWQDqEc3ScZBn4sTthr+48@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Mar 17, 2011 at 6:19 AM, Voils, Steven M <steve(at)sensorswitch(dot)com> wrote:
> Is there a fundamental difference between a primary key and a unique index?
> Currently we have primary keys on tables that have significant amounts of
> updates performed on them, as a result the primary key indexes are becoming
> significantly bloated. There are other indexes on the tables that also
> become bloated as a result of this, but these are automatically rebuild
> periodically by the application (using the concurrently flag) when read
> usage is expected to be very low.
If you're experiencing bloat, but not deleting huge chunks of your
table at a time, then you're not vacuuming aggressively enough
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2011-03-17 18:52:25 | Re: Primary key vs unique index |
| Previous Message | bubba postgres | 2011-03-17 18:36:54 | Re: Is TimeZone applied with TIMESTAMP WITHOUT TIME ZONE and Extract( EPOCH ...)? |