"Tom Lane" <[EMAIL PROTECTED]> writes
>
> Evidently that's not often enough. Or it could be that your
> FSM settings aren't large enough?
>
Setting various proper parameters of FSM is onerous for maintainence. Is
there any plan to make FSM buffer-file-able, just like what clog does now?
Regards
On Mon, Jun 13, 2005 at 22:27:31 +0200,
Együd Csaba <[EMAIL PROTECTED]> wrote:
>
> The critical tables are vacuum analyzed in every hour. (Not vacuum full
> because of the several minutes long exclusive lock)
>
> Earlier the system had been running for 3 months without problems, but a few
> we
=?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes:
> The critical tables are vacuum analyzed in every hour.
Evidently that's not often enough. Or it could be that your
FSM settings aren't large enough?
regards, tom lane
---(end of broadcas
Hi,
there is a very intensively used database. The "usage" means that there are
many-many changes in it. It is 24/7 application.
One table is used to insert 200+ rows per minute from a datacolletor driver
application. 200+ deletions are also performed on the same table. It is very
very important
