From: | "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com> |
---|---|
To: | "Mark Parker" <markus_ext(at)senator(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: another newbie question: PLEASE HELP! |
Date: | 2003-11-25 12:33:23 |
Message-ID: | 200311250433.23518.uwe@oss4u.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
AFAIK no. Vacuum runs in a transaction, so you will only see the effects if it
completed. I think you should run vacuum more often.
It also should work to run vacuum "in operation". i.e. I run vacuum about 4
times a day in an active database. Vacuum doesn't render the database read
only.
On Wednesday 19 November 2003 10:55 pm, Mark Parker wrote:
> What happens if I kill a "vacuum full" in progress? Do I get the freed
> space of the tables processed up till then?
>
> The reason that I ask is that I've been doing a vacuum full for 2.5 hours
> now and I've seen this:
>
> INFO: Pages 66056: Changed 0, reaped 66049, Empty 0, New 0; Tup 1264285:
> Vac 2368115, Keep/VTL 0/0, UnUsed 2711343, MinLen 63, MaxLen 92; Re-using:
> Free/Avail. Space 411271648/411270572; EndEmpty/Avail. Pages 0/66022.
> CPU 5.55s/1.78u sec elapsed 20.13 sec.
> INFO: Index features_group_desc_i: Pages 919085; Tuples 1264285: Deleted
> 2242084.
> CPU 138.02s/23.94u sec elapsed 4681.73 sec.
> INFO: Index features_groupid_i: Pages 517781; Tuples 1264285: Deleted
> 2368115.
> CPU 123.47s/22.16u sec elapsed 2488.06 sec.
> INFO: Index features_featid_i: Pages 518163; Tuples 1264285: Deleted
> 2368115.
> CPU 130.52s/21.41u sec elapsed 2482.68 sec.
> INFO: Index features_pkey: Pages 18351; Tuples 1264285: Deleted 1187073.
> CPU 4.75s/11.34u sec elapsed 141.53 sec.
>
> But there hasn't been any space freed up on the drive. I had to kill the
> process because the system is going to fetch some new data via ftp and the
> db needs to be writable. I just don't understand what the heck is going on.
>
> -Mark
>
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
- --
UC
- --
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/w0wTjqGXBvRToM4RAnutAJ4toreLV3nJLgzyx+g+GibprnKG1wCfTA5H
03aR8BerWzYbDvWtsd1bnRU=
=MPdB
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Uwe C. Schroeder | 2003-11-25 12:49:31 | Re: Lock strategies! |
Previous Message | Oleg Bartunov | 2003-11-25 12:29:32 | Re: tsearch2 column update produces "word too |