From: | "Iain" <iain(at)mst(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: ERROR: canceling query due to user request |
Date: | 2003-12-24 02:10:30 |
Message-ID: | 005201c3c9c3$1b5ecff0$7201a8c0@mst1x5r347kymb |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Tom,
I agree with your assessment of this.
I'm no expert on Linux, and I'm new to Postgres but I'm learning. I hope to
have a chance to play with and test these kinds of configuration settings
before the system goes live. Unfortunately there is no plan for a test
environment that is comparable to the production environment.
By the way, I've been using 7.4 for a little while now (in development) and
my feeling is that the DB has matured considerably since the previous
version I used which was 7.1. It's looking good so far.
Regards
Iain
----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Iain" <iain(at)mst(dot)co(dot)jp>
Cc: <pgsql-admin(at)postgresql(dot)org>
Sent: Saturday, December 20, 2003 3:11 AM
Subject: Re: [ADMIN] ERROR: canceling query due to user request
> "Iain" <iain(at)mst(dot)co(dot)jp> writes:
> > This is typical of the errors I got:
> > pg_dump: ERROR: canceling query due to user request
>
> If you didn't actually do anything to cancel the query, then this
> indicates that something is sending SIGINT signals to the backend
> process. I'd bet on a "ulimit" or equivalent resource-limit setting
> being tripped. Check what conditions the postmaster is being started
> under --- generally, you do not want *any* active ulimit restrictions
> on the server processes.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Iain | 2003-12-24 03:16:42 | Re: FATAL: unrecognized configuration parameter "show_statement_stats" |
Previous Message | Yuji Shinozaki | 2003-12-22 20:17:02 | Re: constaint addition to existing schema |