Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.

From: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>,Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-general(at)postgresql(dot)org,pgsql-patches(at)postgresql(dot)org
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Date: 2005-02-24 22:39:22
Message-ID: Pine.LNX.4.58.0502241437440.13185@greenie.cheapcomplexdevices.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-patches
On Thu, 24 Feb 2005, Tom Lane wrote:
> I preferred Simon's idea of not trying to produce a warning for pages
> when we've detected relation overflow.

Sounds good.  I'll make that update.

Should the relation overflow be a WARNING or a LOG?  It sounds like
if you have that problem it's almost certainly a problem, right?

> Making it a LOG rather than WARNING does address the issue of being
> too much in-your-face for an uncertain condition, though.

Great.

In response to

Responses

pgsql-patches by date

Next:From: Tom LaneDate: 2005-02-24 22:42:13
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Previous:From: Tom LaneDate: 2005-02-24 22:34:57
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.

pgsql-general by date

Next:From: Tom LaneDate: 2005-02-24 22:42:13
Subject: Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Previous:From: Aleksei ValikovDate: 2005-02-24 22:38:09
Subject: Problems with query in highly concurrent environment

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group