From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "angshumitra ghosh" <angshumitrag(at)hotmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Backend crash |
Date: | 2004-05-31 04:30:58 |
Message-ID: | 6969.1085977858@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
"angshumitra ghosh" <angshumitrag(at)hotmail(dot)com> writes:
> Can anyone please tell me why postmaster is shutting down ? What all
> causes the SIGINT signal to be sent to postmaster that causes rollback of
> open transactions and disconnection of open connections ?
I suspect that you are doing something roughly along the lines of
postmaster ... &
psql ...
^C
When you launch the postmaster from an interactive session, it is still
susceptible to being SIGINT'd by your shell unless you take steps to
prevent that. When I need to manually launch a postmaster, I usually
do this sort of thing:
nohup postmaster ...args... </dev/null >logfile 2>&1 &
The combination of nohup and making sure that none of stdin, stdout,
stderr are still connected to your terminal is enough to disconnect
the postmaster from your shell session in the Unixen that I've used.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-31 04:37:40 | Re: determining when a database was created |
Previous Message | Tom Lane | 2004-05-31 04:24:10 | Re: Can't restore from pg_dump. Authentication failed |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-05-31 04:53:00 | Re: Large table search question |
Previous Message | ljb | 2004-05-31 00:31:18 | Re: What does error code PGSQL_TUPLES_OK (2) actually mean? |