Re: pg_ctl reload breaks our client

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

Michael,
It is Postgres 7.3.6. The client is a multi-threaded C++ client. The
breakage was that one group of connections simply stopped. Others
contined without problem. It is not clear exactly what was going on.

Nothing in our application logs gives us any clue to this.

As for reproducibility, it has hapenned before in test environments when
we have bounced the datanase. This is not too shocking as I would
expect the client to notice this :-) It is a little more shocking when
it's a reload. Or maybe I have simply misunderstood what reload does.

I am simply looking for clues here and don't expect definitive answers.
That's why I was a little vague.

Am I right though, in thinking that a reload shuold be pretty much
invisible to the client, or will certain operations fail and require a
re-try?

__
Marc

On Fri, 2005-09-16 at 14:40 -0600, Michael Fuhr wrote:
> On Fri, Sep 16, 2005 at 01:28:13PM -0700, Marc Munro wrote:
> > Yesterday a client application broke immediately after we issued a
> > pg_ctl reload command.
>
> How did the client break? What behavior did it exhibit? Were there
> any errors in the server's logs? Can you duplicate the problem?
> What version of PostgreSQL are you using, and on what platform?
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-09-16 21:51:09 Re: Question about a query plan
Previous Message Bill Moseley 2005-09-16 21:09:01 Re: Setting WHERE on a VIEW with aggregate function.