From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, "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 to user request |
Date: | 2007-12-03 23:37:48 |
Message-ID: | 200712032337.lB3Nbm521738@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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:
> >
> > > I don't know if this is either a wording change, or a more serious bug, but
> > > when I do a pg_restore (from a 8.1.9 setup) to a fresh 8.3beta3 created
> > > database (createdb command only), I repeatedly see:
> > >
> > > 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?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-12-03 23:56:50 | Re: BUG #3790: pg_restore error canceling statement due to user request |
Previous Message | Tom Lane | 2007-12-03 22:38:03 | Re: BUG #3796: crash after select from indexed columns |