| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rickard <David(dot)Rickard(at)GTScompanies(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org, Judith Strawser <judiths(at)GTScompanies(dot)com> |
| Subject: | Re: More Query Cancelled Matters |
| Date: | 2003-09-18 19:51:29 |
| Message-ID: | 1805.1063914689@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
David Rickard <David(dot)Rickard(at)GTScompanies(dot)com> writes:
> We're still encountering situations (vacuum, exports, certain queries &
> psql commands) where PostGreSQL throws a "psql: ERROR: Query was
> cancelled." message;
> Previous enquiries on this issue have received suggestions that something
> on our server may be throwing SIGINTs--but our system people cannot find
> anything that might be causing such events;
> We are attaching our postgresql.conf file, on the off chance that someone
> can see some mis-set value(s) therein;
Like this one?
> statement_timeout = 120 # 0 is disabled, in milliseconds
This will trigger "Query was canceled" for any query running longer than
120 msec, which is not a lot ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | santoso berkah | 2003-09-18 23:38:29 | Re: How to set up postgres user |
| Previous Message | David Rickard | 2003-09-18 19:48:59 | More Query Cancelled Matters |