Re: Terminating a backend

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Terminating a backend
Date: 2008-03-07 01:40:56
Message-ID: 200803070140.m271eu603496@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I have an idea for this TODO item:
> > ...
> > When we get the termination signal, why can't we just set a global
> > boolean, do a query cancel, and in the setjmp() code block check the
> > global and exit --- at that stage we know we have released all locks and
> > can exit cleanly.
>
> How does that differ from what happens now?

We would _terminate_/exit, not just cancel the query.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2008-03-07 04:09:46 Re: Group Commit
Previous Message Tom Lane 2008-03-07 01:34:29 Re: Terminating a backend

Browse pgsql-patches by date

  From Date Subject
Next Message Euler Taveira de Oliveira 2008-03-07 06:14:09 Re: [BUGS] BUG #3975: tsearch2 index should not bomb out of 1Mb limit
Previous Message Tom Lane 2008-03-07 01:34:29 Re: Terminating a backend