After enabling the "no-flush" option, can I force a flush adhoc?

From: David Larson <davidl(at)digitalcyclone(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: After enabling the "no-flush" option, can I force a flush adhoc?
Date: 2000-01-17 15:57:45
Message-ID: 38833BF9.72E92B06@digitalcyclone.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

For performance reasons, everyone is pushing the "no-flush"
option, and I can see why -- it is incredibly fast in comparison
to running without it.

However, I would feel more comfortable if I had an option to
force a flush. There are times during the day when there is
larger amounts of activity, but during the quieter times, I would
like to be able to revert back to the "flush" mode -- because
of the data loss threat.

Is there an API that I can invoke when I deem appropriate?

I would like to be able to either force a flush to occur right
now, or, preferably, to be able to switch operating modes
("flush" or "no-flush") on demand.

Browse pgsql-general by date

  From Date Subject
Next Message Stephane Bortzmeyer 2000-01-17 16:02:33 Re: [GENERAL] cgi with postgres
Previous Message Robert Davis 2000-01-17 15:39:24 Re: [GENERAL] How do you live without OUTER joins?