Re: 3rd time is a charm.....right sibling is not next child crash.

From: Jeff Amiel <jamiel(at)istreamimaging(dot)com>
To: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Amiel <becauseimjeff(at)yahoo(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: 3rd time is a charm.....right sibling is not next child crash.
Date: 2010-06-08 18:19:02
Message-ID: C833F3C6.4B4EA%jamiel@istreamimaging.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


On 6/8/10 1:15 PM, "Jaime Casanova" <jaime(at)2ndquadrant(dot)com> wrote:

> On Tue, Jun 8, 2010 at 12:49 PM, Jeff Amiel <jamiel(at)istreamimaging(dot)com> wrote:
>>
>> ....Does Slony manage it's own vacuuming separate from postgres' autovacuum?
>>
>
> Yes it does: http://www.slony.info/documentation/maintenance.html

" It seems preferable to configure autovacuum to avoid vacuum
Slony-I-managed configuration tables. "

Hmmm....I don't do this.
Surely this is not relative to my corrupt indexes....2 attempted vacuums on
same indexes?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Justin Graf 2010-06-08 18:21:49 Re: Cognitive dissonance
Previous Message Peter Hunsberger 2010-06-08 18:17:56 Re: Queues Problem

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-06-08 18:41:25 Re: Parameters of GiST indexes
Previous Message Jaime Casanova 2010-06-08 18:15:41 Re: 3rd time is a charm.....right sibling is not next child crash.