From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | Francisco Reyes <lists(at)natserv(dot)com> |
Cc: | Medi Montaseri <medi(dot)montaseri(at)intransa(dot)com>, pgsql General List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Closing inactive connections OR user connections limits |
Date: | 2002-11-20 19:32:40 |
Message-ID: | Pine.LNX.4.33.0211201229040.21101-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
On Wed, 20 Nov 2002, Francisco Reyes wrote:
> On Wed, 20 Nov 2002, Medi Montaseri wrote:
>
> > In 7.2, you can run the vacuum in parallel with other database activities...
>
> As far as I know this is not the case for "vacuum full".
The thing that blocks vacuum full are pending transactions. If the
connections aren't holding open a transaction the vacuum full will run
just fine.
For most folks, daily / hourly vacuums (not full vacuums) in 7.2 are
all you need, with a weekly or so vacuum full.
From | Date | Subject | |
---|---|---|---|
Next Message | Medi Montaseri | 2002-11-20 20:07:46 | Re: List of currently connected users |
Previous Message | mallah | 2002-11-20 19:17:58 | Re: [SQL] Drop NOT NULL constraint !!! |
From | Date | Subject | |
---|---|---|---|
Next Message | Dan Langille | 2002-11-20 20:20:15 | Re: Trees: maintaining pathnames |
Previous Message | mallah | 2002-11-20 19:17:58 | Re: [SQL] Drop NOT NULL constraint !!! |