Ok, I'll keep track of how many pages change between updates and play with
the max_fsm_pages value. I'll post my findings.
--Michael
Tom Lane wrote:
"Michael G. Martin" <[EMAIL PROTECTED]> writes:
That's what I was beginning to think from reading. I just wasn't sure
of the cor
"Michael G. Martin" <[EMAIL PROTECTED]> writes:
> That's what I was beginning to think from reading. I just wasn't sure
> of the correlation between MAX_FSM_PAGES and the actual pages occupied
> by the table after a full vacuum. 1:1 ?? Any general rules?
1:1 would be worst case, probably. Th
A "fresh" table with this data has the following pg_class entries:
relname | n
reltype | 265306445
relowner | 503
relam | 0
relfilenode | 265306444
relpages | 429631
reltuples | 2.09533e+07
reltoastrelid | 0
reltoastidxid | 0
relhasindex | f
reli
Thanks Tom,
That's what I was beginning to think from reading. I just wasn't sure of
the correlation between MAX_FSM_PAGES and the actual pages occupied by the
table after a full vacuum. 1:1 ?? Any general rules?
Thanks,
Michael
Tom Lane wrote:
"Michael G. Martin" <[EMAIL PROTECTED]> wr
"Michael G. Martin" <[EMAIL PROTECTED]> writes:
> VACUUM verbose symbol_Data;
> NOTICE: --Relation symbol_data--
> NOTICE: Pages 767990: Changed 0, Empty 0; Tup 21595176: Vac 0, Keep 0,
^^
> UnUsed 16560877.
> Total CPU 61.94s/6.94u sec elapsed 179.25 sec.
That seems t
From what I understand, the new vacuum will mark deleted tuples as
unused and try to re-use the space if possible. However, I seem to have
a huge amount of UnUsed tuples on some large tables. The table is
updated 1x each day followed by a vacuum analyze.
Any idea why the huge UnUsed tuple
What am I missing?
I want to remove a user who owns databases and objects.
I can change the owner of a database by updating the datdba field in
pg_database.
This allows me to drop the user!
However, the user still owns other objects. So, I have found that I also
need to fix ownership for:
pg_
