Re: Cleanly cancel a query.

From: "Thalis A(dot) Kalfigopoulos" <thalis(at)cs(dot)pitt(dot)edu>
To: Dennis <dennis(at)zserve(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Cleanly cancel a query.
Date: 2001-06-08 21:23:02
Message-ID: Pine.LNX.4.21.0106081719190.17741-100000@aluminum.cs.pitt.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

To be more precise, if by "a very large insert" you mean an import of a large data file via COPY, then it is fully transactional i.e. if you kill -TERM the corresponding postmaster, it'll be like the insert never took place.
If you mean multiple INSERTs in a transaction block then again the same.
But if it is a text file with multiple INSERTs just by themselves, I'd guess killing the postmaster would live you with a table only half-full.

cheers,
thalis

On Fri, 8 Jun 2001, Thalis A. Kalfigopoulos wrote:

> You can kill -TERM the postmaster that is executing the particular query.
>
> cheers,
> t.
>
>
> On Fri, 8 Jun 2001, Dennis wrote:
>
> > If I have a database running, and I see that
> > there is a postmaster process taking 99.9% cpu.
> >
> > ie, a very large insert query.
> >
> > Is there a way to cleanly shut down that query from the client or admin
> > side?
> >
> >
> > -Thanks
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Don't 'kill -9' the postmaster
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jonathan Bartlett 2001-06-08 21:42:09 Re: maximum number of rows in table - what about oid limits?
Previous Message Somazx Interesting 2001-06-08 21:06:57 Re: Can not pg_dumpall