| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Autovacuum improvements |
| Date: | 2007-01-14 21:28:54 |
| Message-ID: | 200701142228.57485.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera wrote:
> Hmm, I can see having DROP DATABASE just stopping the autovacuum
> (since the work will be thrown away),
For that same reason DROP DATABASE could just cut all connections to the
database. Or at least queue up and wait until the session is over.
(The latter would correspond to what DROP TABLE does on a table that is
in use.)
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-01-14 22:38:50 | Re: [HACKERS] NaN behavior |
| Previous Message | Neil Conway | 2007-01-14 21:25:51 | Re: -f <output file> option for pg_dumpall |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-01-14 22:38:50 | Re: [HACKERS] NaN behavior |
| Previous Message | Tom Lane | 2007-01-14 21:01:14 | Re: Autovacuum improvements |