bugGNUstep - Bugs: bug #27823, SQLClient drops connections...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #27823: SQLClient drops connections without sending notifications

Submitted by:  Kai Henningsen <kaicats>
Submitted on:  Tue 27 Oct 2009 12:04:04 PM UTC  
 
Category: LibrariesSeverity: 3 - Normal
Item Group: BugStatus: Fixed
Privacy: PublicAssigned to: None
Open/Closed: In Test

Tue 27 Oct 2009 12:59:34 PM UTC, comment #1:

I went through and checked that backends don't call the internal connect/disconnect methods when they should be calling the public versions (which are responsible for sending notifications).
This should be working in svn trunk now.

> Anyway, it seems rather unfriendly (and performance-hostile) to drop
> the connection just because there was an error.


I'm not sure I can agree with that ... if you are causing errors frequently enough for dropping the connection to be a big performance issue then there's probably something wrong with the way you are doing things.

Dropping the connection is a safety feature, to ensure that there is no chance of a connection being left in any sort of confused state by some unanticipated error ... but I wouldn't mind a patch to allow a connection to attempt to recover gracefully as an option instead.

Richard Frith-Macdonald <CaS>
Project Member
Tue 27 Oct 2009 12:04:04 PM UTC, original submission:

Scenario:

You have a connection to a PostgreSQL server.
The server issues an error.

Postgres.m will then close the connection and raise an exception, but will not send out a SQLClientDidDisconnectNotification. For that matter, I've never seen a SQLClientDidConnectNotification either. Presumably that never happens with automatic connects.

This is rather important when there's a need to start every connection with stuff like SET client_encoding = 'UTF8'.

Anyway, it seems rather unfriendly (and performance-hostile) to drop the connection just because there was an error. You cannot always avoid, say, causing a duplicate key error, in a situation where more than one connection is updating.

Kai Henningsen <kaicats>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by CaS (Posted a comment)
  • -unavailable- added by kaicats (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 27 Oct 2009 12:59:34 PM UTCCaSStatusNone=>Fixed
      Open/ClosedOpen=>In Test

    Back to the top


    Powered by Savane 3.1-cleanup1