| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | "pg_ctl -m fast stop" doesn't shut down with active COPY |
| Date: | 2009-03-12 18:25:47 |
| Message-ID: | 1236882347.25953.9.camel@dell.linuxdev.us.dell.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
This is a repost of:
http://archives.postgresql.org/pgsql-general/2009-03/msg00434.php
I didn't get any response, and it appears to be in contradiction to the
docs:
"SIGINT -- The server disallows new connections and sends all existing
server processes SIGTERM, which will cause them to abort their current
transactions and exit promptly."
http://www.postgresql.org/docs/8.3/static/server-shutdown.html
If you have an open COPY and no data is moving, it simply won't
terminate it. You can terminate it with ctrl-C from psql, but not a
SIGINT to the postmaster or a SIGINT or SIGTERM to the backend.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julio Tavares | 2009-03-13 13:43:29 | Help with PostgreSql and OID missmatches when restoring database with lobs |
| Previous Message | Tom Lane | 2009-03-11 21:02:16 | Re: BUG #4700: SIGSEGV with incorrect input to to_char function |