From: | Hannu Krosing <hannu(at)skype(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Dead Space Map |
Date: | 2006-02-28 16:10:05 |
Message-ID: | 1141143005.3864.1.camel@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Ü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.
--------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2006-02-28 16:12:30 | Re: Dead Space Map |
Previous Message | Tom Lane | 2006-02-28 15:59:46 | Re: bug in 7.3.2 |