Something weird is going on with some of mai emails - I tried to send this from
[EMAIL PROTECTED],
then from [EMAIL PROTECTED] and it does not appear in list. Another answer sent
after this
came through in less than 5 min.
Now I removed Tom Lane from To: and moved pgsql-hackers@postgresql.org
On T, 2005-04-26 at 17:54 -0400, Tom Lane wrote:
Hannu Krosing [EMAIL PROTECTED] writes:
Could I avoid having a transaction at all?
Not really; too much of the database access infrastructure is tied to
transaction stuff ... even facilities as basic as memory management.
As VACUUM is not
Hannu Krosing [EMAIL PROTECTED] writes:
A more general solution to the problem VACUUM does not clean dead
tuples fast enough due to an old transaction problem is keeping the
OldestXmin for each table separately as a list of table OIDs in each
PGPROC.
This would be automatically extandable
On E, 2005-05-02 at 10:38 -0400, Tom Lane wrote:
But what about my question about just changing xid in PGPROC ?
Hannu Krosing [EMAIL PROTECTED] writes:
A more general solution to the problem VACUUM does not clean dead
tuples fast enough due to an old transaction problem is keeping the
On E, 2005-04-25 at 11:11 -0400, Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
On Sun, Apr 24, 2005 at 12:02:37PM +0300, Hannu Krosing wrote:
Must some locks also be released an reaquired inside this loop, or is
there something else I should keep in mind when trying to do this ?
Hannu Krosing [EMAIL PROTECTED] writes:
Could I avoid having a transaction at all?
Not really; too much of the database access infrastructure is tied to
transaction stuff ... even facilities as basic as memory management.
As VACUUM is not transactional in the sense that it does not change
