From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tore Halset <halset(at)pvv(dot)ntnu(dot)no> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: ERROR: canceling query due to user request |
Date: | 2004-09-07 18:03:16 |
Message-ID: | 2445.1094580196@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
Tore Halset <halset(at)pvv(dot)ntnu(dot)no> writes:
> I need to debug all of the trafic between the server and the client to
> track down this problem.
I suspect that it's got nothing at all to do with the traffic between
the server and the client, and that the SIGINT is coming from some
outside agency. However, if you want to be sure about it, set the
postmaster's log_min_messages to DEBUG2, and then the next time the
problem happens, look in the postmaster log to see if you see anything
about
processing cancel request: sending SIGINT to process %d
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Garamond | 2004-09-07 18:18:17 | Re: Salt in encrypted password in pg_shadow |
Previous Message | Tom Lane | 2004-09-07 18:00:13 | Re: [PERFORM] Table UPDATE is too slow |
From | Date | Subject | |
---|---|---|---|
Next Message | chinmoy | 2004-09-07 18:57:04 | Customizing SSL with jdbc |
Previous Message | Tore Halset | 2004-09-07 16:23:39 | Re: ERROR: canceling query due to user request |