From PG
http://developer.postgresql.org/docs/postgres/diskusage.html:
(Remember, relpages is only updated by VACUUM and
ANALYZE.)
--- Litao Wu [EMAIL PROTECTED] wrote:
Hi,
After a table analyzed a table, the table's relpages
of pg_class gets updated, but not those of
associated
Litao,
I have some tables and there are almost only
inserts. So I do not care about the dead tuples,
but do care about the statistics.
Then just run ANALYZE on those tables, and not VACUUM.
ANALYZE table-name;
My PG version is 7.3.2.
I would suggest upgrading to 7.3.6; the version you are
Bill,
As a quick fix, since we're upgrading to 7.4.2 in a few weeks anyhow
(which includes pg_autovacuum), I've simply set up an hourly vacuum on
this table. It only takes ~4 seconds to execute when kept up on an
hourly basis. Is there any penalty to vacuuming too frequently, other
than
Hi Josh,
I know that and that is what I am using now.
The problem is I also need to know
the relpages each indexe takes and analyze
seems not update relpages though vacuum and
vacuum analyze do.
According to PG doc:
Remember, relpages is only updated by VACUUM and
ANALYZE
My question is why
Hello Marty,
MS Is that a composite index?
It is a regular btree index. What is a composite index?
My apologies. A composite index is one that consists of multiple fields
(aka multicolumn index). The reason I ask is that it was spending
almost half the time just searching bv_bookgenres,
Read the docs on going SET statement_timeout TO ...;
Chris
Michael Ryan S. Puncia wrote:
Hi,
How can I automatically kill a process in the database (ex a select or
explain) if it exceeds my limit of 2 or 3 mins ..
For example : I have a query that already running for 3 or 4 mins I
want to
