Tom Lane wrote:
Isabella Ghiurea isabella.ghiu...@nrc-cnrc.gc.ca writes:
The issue may be with pg_size_pretty() results, I don't have details
knowledge of this function.
I doubt it, that's a pretty simple function ... but if you don't trust
it, just remove the pg_size_pretty call and
Isabella Ghiurea isabella.ghiu...@nrc-cnrc.gc.ca writes:
SELECT nspname || '.' || relname AS
relation,pg_size_pretty(pg_total_relation_size(nspname || '.' ||
relname)) AS s
ize
FROM pg_class C
LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace)
ORDER BY pg_relation_size(nspname ||
caom.plane_psi1 | 23 MB
caom.metric_i2| 18 MB
Thank you
Isabella
--
View this message in context:
http://www.nabble.com/Re%3A--ADMIN--db-size-and-tables-size-difference-tp25531211p25531211.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com
Isabella Ghiurea isabella.ghiu...@nrc-cnrc.gc.ca writes:
SELECT nspname || '.' || relname AS
relation,pg_size_pretty(pg_total_relation_size(nspname || '.' || relname))
AS s
ize
FROM pg_class C
LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace)
ORDER BY pg_total_relation_size(nspname
://www.nabble.com/Re%3A--ADMIN--db-size-and-tables-size-difference-tp25531211p25531314.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
Isabella Ghiurea isabella.ghiu...@nrc-cnrc.gc.ca writes:
The issue may be with pg_size_pretty() results, I don't have details
knowledge of this function.
I doubt it, that's a pretty simple function ... but if you don't trust
it, just remove the pg_size_pretty call and look directly at the
Hi Pg Admin list.
I'm trying to understand why there are GB's difference when checking
for db size using pg_size_pretty() and querying for tables + indexes
size. .
The sum of tables +index sizes is showing as aprox 6.5GB and
pg_size_pretty(dbname) is coming as 12GB, this are the
Isabella Ghiurea isabella.ghiu...@nrc-cnrc.gc.ca writes:
I'm trying to understand why there are GB's difference when checking
for db size using pg_size_pretty() and querying for tables + indexes
size. .
You are not counting everything --- the total DB size is clearly 12GB,
so the
Naomi Walker nwal...@eldocomp.com writes:
How would one check for catalog bloat?
Like I said:
Try that last query without the namespace restrictions.
Isabella excluded pg_catalog, so if that's where the problem is,
that's why she didn't see it. But let's see the data before
discussing how to
How would one check for catalog bloat? And, if bloated, would unloading
and reloading the database
fix it?
Naomi
3. Bloat in other system catalogs. 5GB of catalog bloat would be
pretty awful, but maybe that's what it is.
Try that last query without the namespace restrictions.
10 matches
Mail list logo