#31 Disconnected Postgres Clients hose the CPU

aolserver3_3_1
closed
nobody
5
2004-06-28
2003-01-23
No

We are using PG 7.3.1 and AOLserver 3.3.1 ad13

sometimes users stop their browser or exit
the session in the middle of a long running SQL SELECT.

the Postgres Postmaster process continues to run
and chew CPU time forever.

It seems to me that when a user terminates the http
connection prematurely - the AOLServer should send an
end of transaction signal via the Postgres driver to the
Postmaster backend process and tell it to abort the
transaction.

This is not happening.

Is there a postgresql.conf parameter that we need to know
about or a secret nsd.tcl parameter that needs to be
tweaked?

Discussion

  • Danny Lieberman

    Danny Lieberman - 2003-01-23
    • summary: Disconnected Postgres Clients host the CPU --> Disconnected Postgres Clients hose the CPU
     
  • Nathan Folkman

    Nathan Folkman - 2003-02-25
    • assigned_to: nobody --> lowen
     
  • Dossy Shiobara

    Dossy Shiobara - 2004-06-28
    • assigned_to: lowen --> nobody
    • status: open --> closed
     
  • Dossy Shiobara

    Dossy Shiobara - 2004-06-28

    Logged In: YES
    user_id=21885

    I'm not sure why this is in the Support Requests tracker, and
    it's not quite a bug. The problem is being able to trigger an
    event upon HTTP client disconnect -- there's currently no
    mechanism for this. So, there's no way for AOLserver to
    signal to Postgres to cancel a long-running query based on
    remote HTTP client disconnect.

    I'm going to close this ticket ...

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks