Yep, typo. Patched to CVS current and backpatched to 7.3.X.
---------------------------------------------------------------------------
pgsql-bugs@postgresql.org wrote:
> Sergey N. Yatskevich (syatskevich@n21lab.gosniias.msk.ru) reports a bug with a severity of 4
> The lower the number the more severe it is.
>
> Short Description
> typing error in src/backend/libpq/be-secure.c ???
>
> Long Description
> In src/backend/libpq/be-secure.c: secure_write
> on SSL_ERROR_WANT_WRITE call secure_read instead
> secure_write again. May be is this a typing error?
>
>
> Sample Code
>
>
> No file was uploaded with this report
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Index: src/backend/libpq/be-secure.c
===================================================================
RCS file: /cvsroot/pgsql-server/src/backend/libpq/be-secure.c,v
retrieving revision 1.26
diff -c -c -r1.26 be-secure.c
*** src/backend/libpq/be-secure.c 14 Feb 2003 00:18:41 -0000 1.26
--- src/backend/libpq/be-secure.c 29 Mar 2003 03:55:09 -0000
***************
*** 338,344 ****
port->count += n;
break;
case SSL_ERROR_WANT_WRITE:
! n = secure_read(port, ptr, len);
break;
case SSL_ERROR_SYSCALL:
if (n == -1)
--- 338,344 ----
port->count += n;
break;
case SSL_ERROR_WANT_WRITE:
! n = secure_write(port, ptr, len);
break;
case SSL_ERROR_SYSCALL:
if (n == -1)
