Ühel kenal päeval, T, 2006-02-28 kell 10:26, kirjutas Tom Lane:
> Hannu Krosing <hannu(at)skype(dot)net> writes:
> > There is no fundamental reason, why vacuum needs to run in a transaction
> > itselt.
> I'll just take one point: you cannot hold locks unless you have a
> transaction, therefore you cannot even look up the catalog info about
> the table you wish to vacuum; let alone prevent someone else from
> dropping the table under you.
> The current bgwriter is incapable of looking at catalog contents as
> such --- it operates only at the level of physical data blocks.
Would'nt it still be possible to drop a table from below bgwriter ?
Or will pgwriter just ignore that.
In response to
pgsql-hackers by date
|Next:||From: Hannu Krosing||Date: 2006-02-28 16:12:30|
|Subject: Re: Dead Space Map|
|Previous:||From: Tom Lane||Date: 2006-02-28 15:59:46|
|Subject: Re: bug in 7.3.2 |