from what i ve read and have i ve seen in practice, i expected it to do
nothing at all. i just wanted to be absolutely sure and that's why i asked
here.
thank you very much for the clarification
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/vacuum-internals-and-perform
MirrorX,
> so when a transaction is still open from a while back (according to the
> transactionID), no 'new dead' tuples can be marked as re-usable space for
> new rows, right? by 'new dead' i mean that for example there is a
> transaction running from 10.00am(with a specific transactionID). when
thx a lot for your answer :)
so when a transaction is still open from a while back (according to the
transactionID), no 'new dead' tuples can be marked as re-usable space for
new rows, right? by 'new dead' i mean that for example there is a
transaction running from 10.00am(with a specific transact
MX,
> to my understanding, vacuum just marks the dead rows of a table so that from
> that point on that space would be re-used for new inserts and new updates on
> that specific table. however, if there is an open transaction, vacuum can
> only do what is described above up to the point that the o
dear all,
i am trying to understand if i am missing something on how vacuum works. i
ve read the manual, and did some research on the web about that but i am
still not sure.
to my understanding, vacuum just marks the dead rows of a table so that from
that point on that space would be re-used for
