Ken Caruso writes:
> Sorry, the actual error reported by CLUSTER is:
> gpup=> cluster verbose tablename;
> INFO: clustering "dbname.tablename"
> WARNING: could not write block 12125253 of base/2651908/652397108
> DETAIL: Multiple failures --- write error might be permanent.
> ERROR: could not
On Sat, Jul 16, 2011 at 8:59 AM, Tom Lane wrote:
> Ken Caruso writes:
> > Had a DB that had bloated due to lots of updates and insuffcient auto
> vacuum
> > settings. Attempted the following in the following order:
>
> > VACUUM VERBOSE full tablename;
> > CLUSTER tablename;
>
> > Did the full fi
Ken Caruso writes:
> Had a DB that had bloated due to lots of updates and insuffcient auto vacuum
> settings. Attempted the following in the following order:
> VACUUM VERBOSE full tablename;
> CLUSTER tablename;
> Did the full first to ensure that the cluster had enough space to run.
> The db ha
Forgot to mention we have streaming replication partner as well that around
the same time stop recovering because a WAL segment could not be found on
the primary.
On Sat, Jul 16, 2011 at 4:05 AM, Ken Caruso wrote:
> Hello,
>
> Had a DB that had bloated due to lots of updates and insuffcient auto
Hello,
Had a DB that had bloated due to lots of updates and insuffcient auto vacuum
settings. Attempted the following in the following order:
VACUUM VERBOSE full tablename;
CLUSTER tablename;
Did the full first to ensure that the cluster had enough space to run.
The db had already been previousl
