From: | Paul van der Linden <paul(dot)doskabouter(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, ronljohnsonjr(at)gmail(dot)com |
Subject: | Re: Safe to delete files? |
Date: | 2019-04-13 14:10:55 |
Message-ID: | CAEC-EqCWQuNeCKAFzN=Vgw7g4EKQWowqcwd1wFSXR6-Pe_8ThQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
It was just 99 files of 1GB each for each id, and no I didn't vacuum.
I did see disk usage dropping quite a lot after dropping those tables
though, so I expected postgres to delete all unneccesary files for all the
tables.
However when checking just now I saw that the files I was referring to were
indeed deleted somehow (don't have an autovacuum running).
So not sure how or why, but my problem is solved
On Sat, Apr 13, 2019 at 2:06 AM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 4/12/19 1:11 PM, Paul van der Linden wrote:
> > Hi,
> >
> > For my process, I needed to drop all the tables in a tablespace except
> > one which I truncated.
> > After that I would have expected to have a couple of KB max in that
> > folder, but there was about 200GB in it.
> >
> > There were 2 sets of files (<id1>, <id1>.1 .. <id1>.99, and the same for
> > id2).
>
> Can you show the actual dir listing?
>
> > Tried the various options from
> > https://blog.2ndquadrant.com/postgresql-filename-to-table/ and oid2name
> > (with -i), to trace it back to a table but all came up empty.
> >
> > Now this folder has a bit of a history spanning several postgres
> > versions and upgrades, and sometime in the past one of the upgrades went
> > horribly wrong, so my first thought was that this was possibly some
> > leftovers from that mishap, but the filetimes were a bit later than that.
> > Also hard to tell because those tables are used as write-once, read-alot
> > so could not base the last usage on filedate.
> >
> > Normally I probably would dare to risk deleting those files, but after
> > the dropping and truncating, the 2 files without extension had the time
> > of drop/truncate and were 0 bytes in length (unfortunately I didn't
> > check the filesize before drop/truncating).
> >
> > Are there other options to see if these files are leftovers from
> > previous stuff and not used by postgres (so i can safely delete them)?
> >
> > Postgres 11, just one used database on it (the other one being a postgis
> > template), running on windows server 2012.
> >
> > In replies please use reply to all...
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-04-13 14:24:45 | Re: Safe to delete files? |
Previous Message | Andreas Kretschmer | 2019-04-13 10:33:04 | Re: SELECT query fails after pg_upgrade as the conditional operator fails |