Re: pg_terminate_backend() issues

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_terminate_backend() issues
Date: 2008-04-16 11:12:47
Message-ID: 874pa2xdcg.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

"Gregory Stark" <stark(at)enterprisedb(dot)com> writes:

> Or weakly -- an assert in CHECK_FOR_INTERRUPTS

oops, that's irrelevant of course.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2008-04-16 14:19:56 pgsql: Avoid using unnecessary pgwin32_safestat in libpq.
Previous Message Gregory Stark 2008-04-16 10:43:00 Re: pg_terminate_backend() issues

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-04-16 12:23:06 Re: pgwin32_safestat weirdness
Previous Message Andrew Chernow 2008-04-16 11:07:38 Re: pulling libpqtypes from queue