| From: | Jim Nasby <decibel(at)decibel(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Have vacuum emit a warning when it runs out of maintenance_work_mem |
| Date: | 2007-05-09 23:18:55 |
| Message-ID: | 788D3DB2-B3C7-49D9-B126-96C58D8E10B3@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On May 9, 2007, at 1:27 PM, Tom Lane 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.
I guess I shouldn't complain since I've made some good money fixing
this in the past. And someone has been posting on -performance this
week with what looks like the same issue.
>> It would be nice to throw them an explicit warning that it's
>> occurring.
>
> I think this is a bad idea. It's furthermore pretty useless in the
> autovacuum world, since no one is likely to see the warning.
Well, it would at least make it into the log file...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Smet | 2007-05-09 23:41:28 | Re: Have vacuum emit a warning when it runs out of maintenance_work_mem |
| Previous Message | Alvaro Herrera | 2007-05-09 20:26:36 | Re: ECPG patch to use prepare for improved performance |