Re: pg_ctl reload breaks our client

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Marc Munro <marc(at)bloodnok(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_ctl reload breaks our client
Date: 2005-09-17 00:20:11
Message-ID: 20050917002011.GA2566@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Sep 16, 2005 at 04:34:46PM -0700, Marc Munro wrote:
> On Fri, 2005-09-16 at 17:10 -0600, Michael Fuhr wrote:
> > Can you reproduce the problem with a reload? A stop and start will
> > terminate client connections, but a reload shouldn't.
>
> This is not currently seen as a priority (the work-around of "don't do
> that" is seen as sufficient). I'm simply hoping to get someone to say
> for sure that the client app should not be able to tell that a reload
> has happened. At that point I may be able to raise the priority of this
> issue.

As far as I know clients shouldn't notice a reload (which is effected
via a SIGHUP); I just did some tests and didn't see any problems.
However, I don't know much about the inner workings of PostgreSQL
so I can't say for sure. Maybe one of the developers will comment.

--
Michael Fuhr

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dann Corbit 2005-09-17 00:43:06 Re: Divide a float4 by 1 - what is going on???????
Previous Message Daniel Schuchardt 2005-09-17 00:12:45 Divide a float4 by 1 - what is going on???????