From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
---|---|
To: | rverghese <riyav(at)hotmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Primary key vs unique index |
Date: | 2012-07-06 17:01:39 |
Message-ID: | 20120706170139.GA17175@depesz.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 06, 2012 at 09:07:53AM -0700, rverghese wrote:
> We are experiencing a similar problem, even though we are on 8.4 and have
> been for a while, and have autovacuum turned on. I have regular concurrent
> reindexes on the indexes but the primary key is seriously bloated. I was
> considering doing the same thing, that is, create another primary key that
> is built on a sequence ( primarily for slony) and then change my current
> multi-column primary key to a unique index. Have you been able to work
> around the problem in any other way?
http://www.depesz.com/2011/07/06/bloat-happens/
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
From | Date | Subject | |
---|---|---|---|
Next Message | ach | 2012-07-06 17:05:08 | index and data tablespaces on two separate drives or one RAID 0? |
Previous Message | Pavel Stehule | 2012-07-06 16:41:52 | Re: Dynamic query execution using array |