| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: signals?? |
| Date: | 2002-10-17 03:52:38 |
| Message-ID: | 6098.1034826758@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> Looking at the Administrators guide (for 7.2.1) it does not list what signals a postgres
> backend handles. I assume HUP makes it reread the config file, but what else is there?
> Is there a way to cancel a currently running query by sending a
> signal?
Sure, SIGINT to a backend implements query-cancel.
You are right that the postmaster and backend signal handlers are poorly
documented --- the details are all there in the sources, but the SGML
docs are pretty thin on the subject :-(. Care to dig around in the code
and submit some doc improvements?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-10-17 04:18:44 | Re: Has anyone seen this SPARC bug? [Fwd: Bug#165060: postgresql: int8 value out of range on sparc] |
| Previous Message | Tom Lane | 2002-10-17 03:36:01 | Re: tuplestore: write failed |