-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10 Jan 2008, at 11:18, Gábor Farkas wrote:
Simon Riggs wrote:
also, even if it is wrong, can an 'idle-in-transaction'
connection that was opened today block the vacuuming of rows that
were deleted yesterday?
Yes, if the rows were deleted after the connection started.
to avoid any potential misunderstandings, i will summarize the
situation:
1. the vacuum-cronjob refuses to remove dead rows since 1.jan.2008.
2. i know that no postgres-process is older than 7.jan.2008. (from
"ps aux | grep postgres", and except the postgres-system-processes)
how can this happen?
To my understanding the question how old the processes are is only
partially of interest,
if a process touches those rows in a transaction just before the
vacuum runs, it can't remove those rows.
So all you need to get in this situation is a transaction that
touches the rows in a transaction and
keeps the transaction alive before vacuum runs.
- --
Viele Grüße,
Lars Heidieker
lars@xxxxxxxxxxxx
http://paradoxon.info
- ------------------------------------
Mystische Erklärungen:
Die mystischen Erklärungen gelten für tief;
die Wahrheit ist, dass sie noch nicht einmal oberflächlich sind.
-- Friedrich Nietzsche
[ Die Fröhliche Wissenschaft Buch 3, 126 ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFHhfwXcxuYqjT7GRYRAoKcAKCZgW/RI9rWN0/Gkd+c7F3T4WmV0gCg4Y6p
VBxOBw50HJYsHBPFUjuaPa4=
=8d+w
-----END PGP SIGNATURE-----
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
