| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, prlw1(at)cam(dot)ac(dot)uk, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] pg_dump disaster |
| Date: | 2000-01-21 22:05:43 |
| Message-ID: | 9725.948492343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alfred Perlstein <bright(at)wintelcom(dot)net> writes:
> We both missed it, and yes it was my fault. All connections are
> behaving as if PQsetnonblocking(conn, TRUE) have been called on them.
> The original non-blocking patches did something weird, they seemed
> to _always_ stick the socket into non-blocking mode. This would
> activate my non-blocking stuff for all connections.
Yes, the present state of the code seems to activate nonblocking socket
mode all the time; possibly we could band-aid our way back to a working
psql by turning off nonblock mode by default. But this doesn't address
the fact that the API of these routines cannot support nonblock mode
without being redesigned.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Tardif | 2000-01-21 23:10:46 | max(oid) |
| Previous Message | Tom Lane | 2000-01-21 22:02:06 | Re: [HACKERS] Re: vacuum timings |