On Friday 14. of May 2010 20:02:02 Tom Lane wrote:
> Rumko writes:
> > On Friday 14. of May 2010 19:29:44 Tom Lane wrote:
> >> Hmm, do both of the toast tables with bloat problems have
> >> "{autovacuum_enabled=false}" ?
> >
> > Yeah, but also
On Friday 14. of May 2010 19:29:44 Tom Lane wrote:
> Rumko writes:
> > On Thursday 13. of May 2010 21:43:37 Tom Lane wrote:
> >> Do *any* of the rows in pg_class have non-null reloptions?
> >
> > First of all, really sorry.
> > "select reloptions from p
On Thursday 13. of May 2010 21:43:37 Tom Lane wrote:
> Rumko writes:
> > As far as I'm concerned, the TOAST table itself does not bother me even
> > if I have a few bytes per row there, only the part where VACUUM claims no
> > free space even though pages are more empty
On Thursday 13. of May 2010 17:24:47 Tom Lane wrote:
> Rumko writes:
> > Tom Lane wrote:
> >> There's something extremely wacko about that vacuum output.
> >
> > Regarding storage paramaters, you mean ALTER TABLE x SET STORAGE...? Then
> > no.
>
>
Tom Lane wrote:
>
> There's something extremely wacko about that vacuum output. A toast
> table should have few, if any, rows that short. And it's impossible
> to believe there's no free space at all in the table, especially since
> 122*3259181 bytes is still quite a lot less than 3259181 pages
Hi!
I'm running 8.4.3 (the exact same problem was also present on 8.4.2) installed
from rpm packages at http://yum.pgsqlrpms.org/ on CentOS 5.4 (x86_64).
I have experienced a bit of a problem with my DB's storage and upon further
investigation, noticed that only some (2 for each day of data) of m
p here)? I
believe it was #5456, but am not 100% sure (bad memory and didn't save the
number).
Thank you
--
Regards,
Rumko
signature.asc
Description: This is a digitally signed message part.
