Re: psql won't stayed connected - Mailing list pgsql-admin

From Kevin Izzet
Subject Re: psql won't stayed connected
Date
Msg-id OFEFB44E5F.D3DCB3A8-ON80256EEB.0051E5AE-80256EEB.00528BD1@nsc.com
Whole thread Raw
In response to psql won't stayed connected  ("Kevin Izzet" <Kevin.Izzet@nsc.com>)
Responses Re: psql won't stayed connected  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin

Hi Tom,

Nope nothing silly, just trying to get a command line connection......

Am I maybe missing some kind of default logicals ?
Am I correct in thinking that apart from compiling the client from source I don't need to modify any of the conf files ?

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

:-(


Regards

Kevin Izzet

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



"Tom Lane" <tgl@sss.pgh.pa.us>

09/08/2004 15:45

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



"Kevin Izzet" <Kevin.Izzet@nsc.com> writes:
> Below is an extract from a truss of the psql login, looks fine to me,

Not really.  Here we have the successful connection to the server:

> 937:    send(4, "\0\0\0 #\003\0\0 u s e r".., 35, 0)    = 35
> 937:    sigaction(SIGPIPE, 0xFFBEEAC8, 0xFFBEEB48)      = 0
> 937:    poll(0xFFBEED78, 1, -1)                         = 1
> 937:    recv(4, " R\0\0\0\b\0\0\0\0 N\0\0".., 16384, 0) = 75
> 937:    write(2, " D E B U G :     I n i t".., 21)      = 21
> 937:    poll(0xFFBEED78, 1, -1)                         = 1
> 937:    recv(4, " S\0\0\01E c l i e n t _".., 16384, 0) = 155

and here is psql doing its normal initialization:

> 937:    access("/home/kevini/.psqlrc-7.4.3", 4)         Err#2 ENOENT
> 937:    access("/home/kevini/.psqlrc", 4)               Err#2 ENOENT
> 937:    getcontext(0xFFBEEDE0)
> 937:    sigaction(SIGINT, 0xFFBEEED8, 0xFFBEEF58)       = 0
> 937:    ioctl(0, TCGETA, 0xFFBEE9BC)                    Err#6 ENXIO
> 937:    fstat64(0, 0xFFBEEA30)                          = 0
> 937:    brk(0x0004CC48)                                 = 0
> 937:    brk(0x0004EC48)                                 = 0

and here it's trying to read the first command from stdin,
and getting EOF back:

> 937:    read(0, 0x0004ADB4, 8192)                       = 0

whereupon it quite correctly decides to close up shop:

> 937:    sigaction(SIGINT, 0xFFBEEED8, 0xFFBEEF58)       = 0
> 937:    sigaction(SIGPIPE, 0xFFBEECC0, 0xFFBEED40)      = 0
> 937:    send(4, " X\0\0\004", 5, 0)                     = 5
> 937:    sigaction(SIGPIPE, 0xFFBEECC0, 0xFFBEED40)      = 0
> 937:    close(4)                                        = 0
> 937:    sigaction(SIGPIPE, 0xFFBEEF10, 0xFFBEEF90)      = 0
> 937:    llseek(0, 0, SEEK_CUR)                          = 0
> 937:    _exit(0)

So why the heck is it getting EOF from stdin?  You're not doing
anything as silly as "psql </dev/null" are you?

                                                  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

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql won't stayed connected
Next
From: "Andrew Parkyns"
Date:
Subject: Re: [PORTS] PostgreSQL Upgrade recommendations