From: | "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Autovacuum in the backend |
Date: | 2005-06-15 09:04:46 |
Message-ID: | d8or3d$1bgq$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu> writes
>
> The start/stop routine is quite like Bgwriter.
>
I just realized that the non-standard backend can't execute any SQL command.
If so, how would the background pg_autovacuum do "vacuum"? It could be
forked more like a standard backend, but this is obviously not a good idea,
since we don't know which database this process will sit on.
A possible solution is that backgroud pg_autovacuum could fork another
process to connect to postmaster as an ordinary backend each time it feels
that a "vacuum" is needed.
Any ideas?
Regards,
Qingqing
From | Date | Subject | |
---|---|---|---|
Next Message | stig erikson | 2005-06-15 09:25:50 | Re: postgresql rpms (7.4.2, 7.4.5, 7.4.8) for redhat 8.0 |
Previous Message | Hannu Krosing | 2005-06-15 08:56:09 | Re: Autovacuum in the backend |
From | Date | Subject | |
---|---|---|---|
Next Message | Roman Neuhauser | 2005-06-15 09:43:58 | Re: how to return a result set from a stored procedure |
Previous Message | Hannu Krosing | 2005-06-15 08:56:09 | Re: Autovacuum in the backend |