| From: | "Jeffrey Baker" <jwbaker(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: meaning of backend exit code 2? |
| Date: | 2008-06-04 18:46:43 |
| Message-ID: | fd145f7d0806041146j1b17710fw8e193bfcfbdc0941@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 4, 2008 at 11:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Jeffrey Baker" <jwbaker(at)gmail(dot)com> writes:
> > I have a need to find out the meaning of a backend exiting unexpectedly
> with
> > exit code 2. Leafing through the source of 8.1 I can't really find it.
>
> But are you running 8.1? In 8.2 and up this is the expected result from
> SIGQUIT.
Yes, I'm running 8.1.9. I have a strong suspicion that the exit is coming
either from R via pl/R or from perl via pl/perl. From my reading of the
code, expected backend exit codes are 1, 0, and -1 mainly?
-jwb
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2008-06-04 18:55:53 | Re: Overhauling GUCS |
| Previous Message | Tom Lane | 2008-06-04 18:31:27 | Re: meaning of backend exit code 2? |