Ühel kenal päeval, K, 2006-08-23 kell 05:23, kirjutas Gregory Stark:
With all this code to handle ignoring vacuum transactions in calculating the
global xmin it just occurred to me to wonder: Does lazy vacuum need a
transaction at all? It doesn't do the tuple moving tricks with xvac that
Hannu Krosing [EMAIL PROTECTED] writes:
When I asked the same question, I was told that a lot of core
functionality vacuum uses needs to be in transaction. I guess bad things
can happen, if some other backend ends a transaction you claim to be in.
And it is not so much about what ends up
Ühel kenal päeval, K, 2006-08-23 kell 08:11, kirjutas Greg Stark:
Hannu Krosing [EMAIL PROTECTED] writes:
BTW, I think that CONCURRENT CREATE INDEX should be modified to use long
transactions which actually build the index and are ignored by vacuum
and short ones which write data to system
Gregory Stark wrote:
With all this code to handle ignoring vacuum transactions in calculating the
global xmin it just occurred to me to wonder: Does lazy vacuum need a
transaction at all? It doesn't do the tuple moving tricks with xvac that
vacuum full does so does lazy vacuum's xid ever
Hannu Krosing [EMAIL PROTECTED] writes:
Ãhel kenal päeval, K, 2006-08-23 kell 05:23, kirjutas Gregory Stark:
global xmin it just occurred to me to wonder: Does lazy vacuum need a
transaction at all?
When I asked the same question, I was told that a lot of core
functionality vacuum uses
