Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Kill a session
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Craig A. James" <cjames(at)modgraph-usa(dot)com>
- Cc: pgsql-performance(at)postgresql(dot)org, sgunderson(at)bigfoot(dot)com
- Subject: Re: Kill a session
- Date: Fri, 14 Jul 2006 12:25:13 -0400
- Message-id: <22033.1152894313@sss.pgh.pa.us> <text/plain>
"Craig A. James" <cjames(at)modgraph-usa(dot)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
- References:
- Re: Kill a session
- From: Magnus Hagander
- Re: Kill a session
- From: Craig A. James
- Re: Kill a session
- From: Steinar H. Gunderson
- Re: Kill a session
- From: Craig A. James
- Re: Kill a session
- From: Tom Lane
- Re: Kill a session
- From: Craig A. James
- Re: Kill a session
- Prev by Date: Re: Kill a session
- Next by Date: Self-join query and index usage
- Previous by thread: Re: Kill a session
- Next by thread: Re: Kill a session
- Indexes: