Skip site navigation (1) Skip section navigation (2)

Re: Ye olde drop-the-database-you-just-left problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Ye olde drop-the-database-you-just-left problem
Date: 2007-05-30 20:27:40
Message-ID: 18407.1180556860@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Gregory Stark <stark(at)enterprisedb(dot)com> writes:
> Is there any way to tell, perhaps from the command string, that the process is
> about to start exiting? What stage of exiting is it that we think the kernel
> goes to lunch?

I haven't really done any detailed investigation, but I would think that
a simple process exit (when there's not temp tables to drop or anything
like that) should complete within one scheduler timeslice.  That would
mean that when this problem occurs, it's usually because the kernel hasn't
scheduled the backend at all since the disconnect message was sent;
which in turn means there is no way at all to know that the backend is
going to exit when it does get a chance to run.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2007-05-30 21:09:55
Subject: Re: [COMMITTERS] pgsql: Make large sequential scans and VACUUMs work in a limited-size
Previous:From: Bruce MomjianDate: 2007-05-30 20:26:13
Subject: Re: Padding on 64-bit

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group