At 01:48 PM 1/1/00 -0500, Tom Lane wrote:
>I said no such thing!
>
>You certainly *can* reconnect, although under WAL it will take a delay
>(or better, a retry loop).
>
>However, I think reconnection has to be integrated into the
>application's logic at a level where you can have some idea of what
>needs to be redone after reconnecting. That's why I objected to having
>psql do it. If psql's only going to do it interactively then I guess
>it's safe enough, though.
OK, my misunderstanding. I couldn't understand why psql in interactive
mode should be a problem and took your comments in a more general context.
>
>Question for discussion: when the WAL postmaster is running a database
>start or restart, perhaps it should simply delay processing of new
>connection requests until the DB is ready, instead of rejecting them
>immediately? That would eliminate the need for retry loops in
>applications, and thereby avoid wasted retry processing on both sides.
>On the other hand, I can see where an unexpected multi-second delay to
>connect might be bad news, too. Comments?
I've been thinking about this one, actually...
Perhaps letting the caller decide in some manner? In my driver environment
I'm not really supposed to call sleep or the like and a busy-wait for the
connection(s) to be rebuilt probably isn't the best thing to do, since the
postmaster is going to be hard at work straightening out things with the
WAL.
- Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert
Serviceand other goodies at http://donb.photo.net.
