pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Craig A. James <cjames@modgraph-usa.com>
Cc: pgsql-performance@postgresql.org
Cc: sgunderson@bigfoot.com
Subject: Re: Kill a session
Date: Fri, 14 Jul 2006 12:25:13 -0400
Message-ID: <22033.1152894313@sss.pgh.pa.us> (raw)
In-Reply-To: <44B7B592.1090405@modgraph-usa.com>
References: <6BCB9D8A16AC4241919521715F4D8BCEA0FAE8@algol.sollentuna.se>
	<44B51896.1000808@modgraph-usa.com>
	<20060712170404.GA27392@uio.no>
	<44B70017.6000703@modgraph-usa.com>
	<8780.1152856222@sss.pgh.pa.us>
	<44B7B592.1090405@modgraph-usa.com>

"Craig A. James" <cjames@modgraph-usa.com> writes:
> It's also possible that the INSERT itself is the problem, or adds to the problem.  The SIGINT may come after a few million rows have been inserted, so it would have to clean that up, right?

No, because we don't use UNDO.  The next VACUUM would have a bit of a
mess to clean up, but you wouldn't pay for it at the time of the abort.

			regards, tom lane

view thread (14+ messages)

Message-ID: <22033.1152894313@sss.pgh.pa.us>
Permalink:  ../22033.1152894313@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/22033.1152894313@sss.pgh.pa.us

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, cjames@modgraph-usa.com, sgunderson@bigfoot.com
  Subject: Re: Kill a session
  In-Reply-To: <22033.1152894313@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox