Re: Have vacuum emit a warning when it runs out of maintenance_work_mem

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-patches(at)postgresql(dot)org
Cc: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jim Nasby" <decibel(at)decibel(dot)org>
Subject: Re: Have vacuum emit a warning when it runs out of maintenance_work_mem
Date: 2007-05-12 02:18:30
Message-ID: 200705112218.31033.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Wednesday 09 May 2007 19:41, Guillaume Smet wrote:
> On 5/9/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Jim Nasby <decibel(at)decibel(dot)org> writes:
> > > Any time this happens it's generally a nasty surprise for users.
> >
> > Really? Running out of work memory is expected on large tables.
>
> Sure. Perhaps we should find a better error message but it's an
> interesting information. Personnaly, I try to choose a sane value
> depending on my database but I'm never sure it's really sufficient or
> if I added 100MB it would have made a real difference.
>

If we were going to implement this (and I'm a tad skeptical as well), wouldn't
it be better if the warning occured at the end of vacuum, and told you how
much memory was actually needed, so you'd know what maintainence_work_mem
should be.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Henry B. Hotz 2007-05-12 16:53:49 Re: Preliminary GSSAPI Patches
Previous Message Tomas Doran 2007-05-12 02:16:03 Re: Implemented current_query