Bruce Momjian escribió:
> Simon Riggs wrote:
> > On Thu, 2007-03-01 at 22:35 +0530, Pavan Deolasee wrote:
> > > Merlin Moncure wrote:
> > > > On 3/1/07, Pavan Deolasee <pavan(dot)deolasee(at)enterprisedb(dot)com> wrote:
> > > >>
> > > > seems pretty solid except for one possible problem...at one point when
> > > > I dropped then later added the index on 'abalance', I got spammed
> > > > 'WARNING: found a HOT-updated tuple' from psql prompt.
> > >
> > > Thats intentional. We don't yet support CREATE INDEX on a HOT-updated
> > > table. This is one of the major unfinished TODO items before we can
> > > consider patch feature complete. I have left the warning to catch
> > > this case till then.
> > CREATE INDEX and VACUUM FULL will require changes. Proposals for VACUUM
> > FULL have been posted, CREATE INDEX should be there tomorrow.
> > CLUSTER does not need changes for HOT, as things stand currently, mainly
> > because its MVCC behaviour is broken.
> That's oddly discouraging. :-)
Apparently no one has been bothered enough to fix CLUSTER.
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
In response to
pgsql-hackers by date
|Next:||From: Darcy Buskermolen||Date: 2007-03-02 21:41:18|
|Subject: Re: Possible Bug: high CPU usage for stats collector in 8.2|
|Previous:||From: Tom Lane||Date: 2007-03-02 20:55:05|
|Subject: Re: [HACKERS] Deadlock with pg_dump? |