Mark Lewis <[EMAIL PROTECTED]> writes:
> You really, really want to upgrade as soon as possible,
No, sooner than that. Show your boss the list of known
data-loss-causing bugs in 7.2.1, and refuse to take responsibility
if the database eats all your data before the "in good time" upgrade.
The rel
On Mon, Jan 30, 2006 at 03:26:23PM -0800, Mark Lewis wrote:
> You have lots of dead rows. Do a vacuum full to get it under control,
> then run VACUUM more frequently and/or increase your FSM settings to
> keep dead rows in check. In 7.2 vacuum is pretty intrusive; it will be
> much better behaved
pgsql-performance@postgresql.org
Sent: Mon, 30 Jan 2006 23:57:11 +0100
Subject: [PERFORM] Query planner issue
> Hi everybody,
>
> I have the following problem, on a test server, if I do a fresh import
> of production data then run
> 'explain analyze select count(*) from mandat
You have lots of dead rows. Do a vacuum full to get it under control,
then run VACUUM more frequently and/or increase your FSM settings to
keep dead rows in check. In 7.2 vacuum is pretty intrusive; it will be
much better behaved once you can upgrade to a more recent version.
You really, really
Hi everybody,
I have the following problem, on a test server, if I do a fresh import
of production data then run
'explain analyze select count(*) from mandats;'
I get this result:
Aggregate (cost=6487.32..6487.32 rows=1 width=0) (actual time=607.61..607.61
rows=1 loops=1)
-> Seq Scan on ma
