"Alvaro Herrera" <[EMAIL PROTECTED]> writes: > Bruce Momjian escribió: >> Magnus Hagander wrote: >> > On Fri, Nov 30, 2007 at 10:13:53AM +0000, Gregory Stark wrote: >> > > >> > > "Mike C." <[EMAIL PROTECTED]> writes: >> > > >> > > > ERROR: canceling statement due to user request >> > > > CONTEXT: automatic analyze of table "dbs.public.entity_event" >> > > >> > > This is intentional, though perhaps the wording is confusing. What >> > > impression >> > > does the wording give you? Does it make you think something has gone >> > > wrong? >> > >> > The fact that it says ERROR kind of hints that something has gone wrong, >> > no? (so yes, I agree the wording isn't very good) >> >> What is causing this? Statement_timeout? I see different wording for >> that behavior. Is the postmaster getting a signal from somewhere on the >> system? > > It's the new autovacuum cancel stuff.
I guess we should capture this error with a PG_TRY and silently abort instead. Just a NOTICE or INFO should be sufficient. Other errors should of course be rethrown. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
