From: | Denis Perchine <dyp(at)perchine(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: libpq error codes |
Date: | 2000-06-22 06:55:27 |
Message-ID: | 00062214003002.00479@dyp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-patches |
> Works the same for me with either pipe or socket connection. I think
> something must be broken on your platform --- what platform are you
> using, anyway?
Linux. I've tested this with 2.2.15pre7 & 2.4.0test1-ac22-riel kernels.
> > db=> select count(*) from pg_class;
> > pqReadData() -- read() failed: errno=32
> >
>
> The two obvious questions about this are (a) what is errno 32 on
> your system and (b) why is your strerror() yielding garbage instead
> of an appropriate error message?
a. It's broken pipe
b. Sorry, it's (a) in russian.
> On my system errno 32 is EPIPE, but surely read() should never
> return EPIPE.
That's right... But what should read return if connection is closed by other side?
--
Sincerely Yours,
Denis Perchine
----------------------------------
E-Mail: dyp(at)perchine(dot)com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-22 07:30:19 | Re: libpq error codes |
Previous Message | Tom Lane | 2000-06-22 06:15:30 | Re: libpq error codes |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-22 07:05:00 | Re: Big 7.1 open items |
Previous Message | Philip J. Warner | 2000-06-22 06:32:56 | Re: Big 7.1 open items |