Re: psql won't stayed connected

Ok get to the Donkey Ears for this week...... :-(

We run all our apps from a central Linux HA service, when we add a new app
we add a new link via a wrapper which allows the
app to choose the correct OS and path for running that app........

The default for the apps is to have an & at the end of the command line so that the command is
spawned.........ooooooooooppppppppsssssssss

So psql was doing exactly what I asked it too, running and
backgrounding..... DUH...........

Apologies for wasting your time Tom, will have to drink more black coffee
and try not to multi task so much..............

Regards

Kevin Izzet

Database / Unix Administrator
Tel: (Code)+44(0)1475 655606
Fax: (Code)+44(0)1475 637755
Email: Kevin(dot)Izzet(at)nsc(dot)com

"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
09/08/2004 16:45

To: "Kevin Izzet" <Kevin(dot)Izzet(at)nsc(dot)com>
cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] psql won't stayed connected

"Kevin Izzet" <Kevin(dot)Izzet(at)nsc(dot)com> writes:
> Am I maybe missing some kind of default logicals ?

Darn if I know.

> The fact that I get the same result from a Linux Client as a Solaris
> client may point to something I've configured wrongly......

I could believe that on Solaris but on Linux it's very unlikely that the
default configuration wouldn't work. The common factor is more likely
pilot error ;-). How *exactly* are you invoking psql, anyway? Could
we see a cut-and-paste from your terminal session?

regards, tom lane

*************************************************************************************
This email may contain confidential and privileged material for the sole
use of the intended recipient. Any review, use, distribution or disclosure
by others is prohibited. If you are not the intended or authorised
recipient please contact the sender by reply email and delete all copies
of this message