Search Postgresql Archives

Re: truncating or full vacuuming

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Wed, Oct 20, 2010 at 4:50 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
=?UTF-8?Q?Viktor_Bojovi=C4=87?= <viktor.bojovic@xxxxxxxxx> writes:
> while creating an index on billion records table i have canceled creation
> because index took me ~70GB of space.
> When I looked into disk space i saw that space is still occupied , and the
> index doesn't exist.

hmm ... was your version of "cancel" spelled "kill -9" or something like
that? ÂIf so it's unsurprising that temp files would have been left
behind. ÂLook in the pgsql_tmp subdirectory. ÂIt's also possible that
the partially-filled index files are still there but aren't linked to
by any live pg_class row. ÂCheck for files that don't match any entry in
the pg_class.relfilenode column. ÂIn both cases you'd have to remove any
such files by hand --- VACUUM is not going to fix this for you.

           Âregards, tom lane

i have used Ctrl+C while i was in console.
I entered into that directory you have mentioned, but i have found no files inside.

postgres@zohar:/srv/postgresql/base$ du -h --max-depth=1
4.2M ./1
4.2M ./11510
4.3M ./11511
1.1G ./1044080708
0 ./pgsql_tmp
453G ./1051277744
454G .





--
---------------------------------------
Viktor BojoviÄ
---------------------------------------
Wherever I go, Murphy goes with me

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux