On 09/21/2011 11:20 AM, Venkat Balaji wrote:
It is very important to remove it from the WIKI page.
Removing it is a little premature. :) Definitely going to add a warning
about relying on its output, though. The query itself was created and
integrated into the check_postgres.pl nagios plugin
It is very important to remove it from the WIKI page.
I ran it on production PG9.0 and it does not error out and displays numbered
output.
I noticed that, this works till PG-8.2 (as per the message).
Venkat
On Wed, Sep 21, 2011 at 8:25 PM, Shaun Thomas wrote:
> On 09/21/2011 09:12 AM, Tom Lan
On 09/21/2011 08:43 AM, Guillaume Cottenceau wrote:
AI Rumman writes:
Using the query http://wiki.postgresql.org/wiki/Show_database_bloat, I got the
Is this stuff to show database bloat reliable?
Only in that increase and decreases of the number reported can be useful
for determi
On 09/21/2011 09:12 AM, Tom Lane wrote:
The PG wiki is editable by anyone who signs up for an account. Feel
free to put in an appropriate disclaimer, or improve the sample
query.
Ah, well then. I do have an account, but thought there were more
granular page restrictions than that. I may have
On Sep 21, 2011, at 8:30 AM, Shaun Thomas wrote:
> I wish they would erase that Wiki page, or at least add a disclaimer.
The "they" that you refer to includes you. It's a wiki. You can write your
own disclaimer.
xoa
--
Andy Lester => a...@petdance.com => www.petdance.com => AIM:petdance
Shaun Thomas writes:
> On 09/21/2011 02:01 AM, AI Rumman wrote:
>> Using the query http://wiki.postgresql.org/wiki/Show_database_bloat,
>> I got the following result for a table:
> God. I wish they would erase that Wiki page, or at least add a
> disclaimer. That query is no better than a loose e
On 09/21/2011 02:01 AM, AI Rumman wrote:
Using the query http://wiki.postgresql.org/wiki/Show_database_bloat,
I got the following result for a table:
God. I wish they would erase that Wiki page, or at least add a
disclaimer. That query is no better than a loose estimate. Never, ever,
ever de
AI Rumman writes:
> Using the query http://wiki.postgresql.org/wiki/Show_database_bloat, I got the
Is this stuff to show database bloat reliable? After a VACUUM
FULL of the table reported as the top responsible of bloat,
performing the same request again still gives the same result
(still that t
On Wed, 2011-09-21 at 13:01 +0600, AI Rumman wrote:
> I am using Postgresql 9.0.1.
>
> I REINDEXED both the indexes and table, but I did not find any change
> in wastedspace or wastedispace.
> Could you please tell me why?
you need to
1) either vacuum full or cluster the table
2) analyze the
Yes I ANALYZE the table, but no change for wastedispace.
On Wed, Sep 21, 2011 at 1:06 PM, Guillaume Lelarge
wrote:
> On Wed, 2011-09-21 at 13:01 +0600, AI Rumman wrote:
> > I am using Postgresql 9.0.1.
> >
> > Using the query http://wiki.postgresql.org/wiki/Show_database_bloat, I
> got
> > the fo
Could you please let us know if you have analyzed after the re-indexing is
done ?
This must show differences for only Indexes not the Tables.
For Tables, you need to do VACUUM FULL to show the difference.
Thanks
Venkat
On Wed, Sep 21, 2011 at 12:31 PM, AI Rumman wrote:
> I am using Postgresql
On Wed, 2011-09-21 at 13:01 +0600, AI Rumman wrote:
> I am using Postgresql 9.0.1.
>
> Using the query http://wiki.postgresql.org/wiki/Show_database_bloat, I got
> the following result for a table:
>
> -[ RECORD 1 ]+---
> current_database | crm
> sc
12 matches
Mail list logo
