From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Magnus Hagander" <magnus(at)hagander(dot)net>, "Mike C(dot)" <smith(dot)not(dot)western(at)gmail(dot)com>, <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #3790: pg_restore error canceling statement due touser request |
Date: | 2007-12-04 07:54:34 |
Message-ID: | 878x4asxmt.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Alvaro Herrera" <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Bruce Momjian escribió:
>> Magnus Hagander wrote:
>> > On Fri, Nov 30, 2007 at 10:13:53AM +0000, Gregory Stark wrote:
>> > >
>> > > "Mike C." <smith(dot)not(dot)western(at)gmail(dot)com> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Rikardo Tinauer | 2007-12-04 11:56:31 | BUG #3798: Add fuzzy string search in TSearch2 |
Previous Message | Thomas H. | 2007-12-04 03:36:06 | Re: BUG #3766: tsearch2 index creation error |