Hello,
I am running Postgres 9.0.4 on Ubuntu 10.0.4.2 in a continuos archive setup
with weekly base backups. I am interested in using pg_compress/pg_decompress
to reduce storage needs. I currently use bzip2 which usually results in 50%
compression, however it appears that pg_compress will provide
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
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 in
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;
> > CLUS
On Sat, Jul 16, 2011 at 2:30 PM, Tom Lane wrote:
> 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 b
On Sun, Jul 17, 2011 at 3:04 AM, Cédric Villemain <
cedric.villemain.deb...@gmail.com> wrote:
> 2011/7/17 Ken Caruso :
> >
> >
> > On Sat, Jul 16, 2011 at 2:30 PM, Tom Lane wrote:
> >>
> >> Ken Caruso writes:
> >> > Sorry, the actual
On Sun, Jul 17, 2011 at 3:04 AM, Cédric Villemain <
cedric.villemain.deb...@gmail.com> wrote:
> 2011/7/17 Ken Caruso :
> >
> >
> > On Sat, Jul 16, 2011 at 2:30 PM, Tom Lane wrote:
> >>
> >> Ken Caruso writes:
> >> > Sorry, the actual
Hello,
I am trying to trouble shoot a couple of issue related to vacuum and db
size. I currently have a postgres DB that is around 390GB on disk (du -hs in
$PG_DATA/base). If I look at the total relation size using the following
query:
SELECT SUM(pg_relation_size(pg_class.oid))
FROM pg_class ;
T
On Tue, Jul 19, 2011 at 1:50 PM, Kevin Grittner wrote:
> Ken Caruso wrote:
>
>
> > SELECT SUM(pg_relation_size(pg_class.oid))
> > FROM pg_class ;
>
> Perhaps you want pg_total_relation_size()?
>
> -Kevin
>
The number returned when using pg_total_relation s
On Tue, Jul 19, 2011 at 2:26 PM, Tom Lane wrote:
> Ken Caruso writes:
> > I am trying to trouble shoot a couple of issue related to vacuum and db
> > size. I currently have a postgres DB that is around 390GB on disk (du -hs
> in
> > $PG_DATA/base). If I look at the total
10 matches
Mail list logo
