aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2002-08-30 16:00:41 +0000
committerBruce Momjian <bruce@momjian.us>2002-08-30 16:00:41 +0000
commitf7e089b3fac5af49815e5cda2e0c3a05625eea19 (patch)
tree31f848f12d74a259bdce1650f620d50e53fc326b
parent9a0b4d7f847469544798133391e221481548e1b9 (diff)
downloadpostgresql-f7e089b3fac5af49815e5cda2e0c3a05625eea19.tar.gz
postgresql-f7e089b3fac5af49815e5cda2e0c3a05625eea19.zip
Back out password packet length check.
Improve wording of pre-7.3 syntax mention.
-rw-r--r--doc/src/sgml/ref/copy.sgml4
-rw-r--r--doc/src/sgml/ref/select.sgml4
-rw-r--r--src/backend/libpq/auth.c16
3 files changed, 5 insertions, 19 deletions
diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index c5c8fcbb947..677ec5792a9 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.38 2002/08/30 03:18:23 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.39 2002/08/30 16:00:41 momjian Exp $
PostgreSQL documentation
-->
@@ -700,7 +700,7 @@ ZW ZIMBABWE
There is no <command>COPY</command> statement in SQL92.
</para>
<para>
- The following syntax was used by pre-7.3 servers and is still supported:
+ The following syntax was used by pre-7.3 applications and is still supported:
<synopsis>
COPY [ BINARY ] <replaceable class="parameter">table</replaceable> [ WITH OIDS ]
FROM { '<replaceable class="parameter">filename</replaceable>' | <filename>stdin</filename> }
diff --git a/doc/src/sgml/ref/select.sgml b/doc/src/sgml/ref/select.sgml
index 1feaa6f7b48..7192de53e0d 100644
--- a/doc/src/sgml/ref/select.sgml
+++ b/doc/src/sgml/ref/select.sgml
@@ -1,5 +1,5 @@
<!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.59 2002/08/30 03:18:23 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.60 2002/08/30 16:00:41 momjian Exp $
PostgreSQL documentation
-->
@@ -869,7 +869,7 @@ SELECT name FROM distributors ORDER BY code;
FOR UPDATE cannot be used in contexts where returned rows can't be clearly
identified with individual table rows; for example it can't be used with
aggregation. FOR UPDATE may also appear before LIMIT for portability with
- pre-7.3 servers.
+ pre-7.3 applications.
</para>
</refsect2>
diff --git a/src/backend/libpq/auth.c b/src/backend/libpq/auth.c
index fb43f8e4af8..216343f36c9 100644
--- a/src/backend/libpq/auth.c
+++ b/src/backend/libpq/auth.c
@@ -8,7 +8,7 @@
*
*
* IDENTIFICATION
- * $Header: /cvsroot/pgsql/src/backend/libpq/auth.c,v 1.87 2002/08/29 21:50:36 momjian Exp $
+ * $Header: /cvsroot/pgsql/src/backend/libpq/auth.c,v 1.88 2002/08/30 16:00:41 momjian Exp $
*
*-------------------------------------------------------------------------
*/
@@ -709,20 +709,6 @@ recv_and_check_password_packet(Port *port)
if (pq_eof() == EOF || pq_getint(&len, 4) == EOF)
return STATUS_EOF; /* client didn't want to send password */
- /*
- * Since the remote client has not yet been authenticated, we need
- * to be careful when using the data they send us. The 8K limit is
- * arbitrary, and somewhat bogus: the intent is to ensure we don't
- * allocate an enormous chunk of memory.
- */
-
- if (len < 1 || len > 8192)
- {
- elog(LOG, "Invalid password packet length: %d; "
- "must satisfy 1 <= length <= 8192", len);
- return STATUS_EOF;
- }
-
initStringInfo(&buf);
if (pq_getstr(&buf) == EOF) /* receive password */
{