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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com>
Cc: 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:34:57
Message-ID: 28095.1109284497@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-patches

Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> writes:
> Would the updated patch below address most of the concerns?

I preferred Simon's idea of not trying to produce a warning for pages
when we've detected relation overflow.

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

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Aleksei Valikov 2005-02-24 22:38:09 Problems with query in highly concurrent environment
Previous Message Tom Lane 2005-02-24 22:25:10 Re: basic trigger using OLD not working?

Browse pgsql-patches by date

  From Date Subject
Next Message Ron Mayer 2005-02-24 22:39:22 Re: [PATCHES] A way to let Vacuum warn if FSM settings are low.
Previous Message Bruce Momjian 2005-02-24 22:28:44 Re: [PATCHES] [pgsql-hackers-win32] Repleacement for src/port/snprintf.c