Re: Extra files in "base" dir not seen in relfilenodes
От | Daniel Farina |
---|---|
Тема | Re: Extra files in "base" dir not seen in relfilenodes |
Дата | |
Msg-id | CACN56+Pb+XH_8iu=jcmAk4QcuGwahHY7geft14jaAZk6T-48oA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Extra files in "base" dir not seen in relfilenodes (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Extra files in "base" dir not seen in relfilenodes
|
Список | pgsql-general |
On Tue, Jan 16, 2018 at 3:04 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Daniel Farina <daniel@fdr.io> writes:
> I am looking at a database with a wide (~500G) divergence between the total
> space expended by the database directory and the result of select
> sum(pg_relation_size(oid)) from pg_class;.
Odd.
> I located about 280G of apparent extra space by performing an anti-join
> between files on disk and files in the catalog via the pg_class.relfilenode
> field.
Umm ... are you accounting for catalogs that have zeroes in
pg_class.relfilenode? It's generally better to rely on the
pg_relation_filenode(oid) function than the raw column contents.
Yeah, the catalogs are not considered here (oids < 10000). The oids in question are rather high. Let me re-run the antijoin with the function though....
Indeed, same result.
В списке pgsql-general по дате отправления: