database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-13 07:41:39 +03:00
Code Activity

Back out password packet length check.

Browse Source 
Improve wording of pre-7.3 syntax mention.
This commit is contained in:
Bruce Momjian
2002-08-30 16:00:41 +00:00
parent 9a0b4d7f84
commit f7e089b3fa
3 changed files with 5 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/ref/copy.sgml
View File

@ -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 PostgreSQL documentation
--> -->
@ -700,7 +700,7 @@ ZW ZIMBABWE
There is no <command>COPY</command> statement in SQL92. There is no <command>COPY</command> statement in SQL92.
</para> </para>
<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> <synopsis>
COPY [ BINARY ] <replaceable class="parameter">table</replaceable> [ WITH OIDS ] COPY [ BINARY ] <replaceable class="parameter">table</replaceable> [ WITH OIDS ]
FROM { '<replaceable class="parameter">filename</replaceable>' | <filename>stdin</filename> } FROM { '<replaceable class="parameter">filename</replaceable>' | <filename>stdin</filename> }

4
doc/src/sgml/ref/select.sgml
View File

@ -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 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 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 identified with individual table rows; for example it can't be used with
aggregation. FOR UPDATE may also appear before LIMIT for portability with aggregation. FOR UPDATE may also appear before LIMIT for portability with
pre-7.3 servers. pre-7.3 applications.
</para> </para>
</refsect2> </refsect2>

16
src/backend/libpq/auth.c
View File

@ -8,7 +8,7 @@
* *
* *
* IDENTIFICATION * 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) if (pq_eof() == EOF || pq_getint(&len, 4) == EOF)
return STATUS_EOF; /* client didn't want to send password */ 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); initStringInfo(&buf);
if (pq_getstr(&buf) == EOF) /* receive password */ if (pq_getstr(&buf) == EOF) /* receive password */
{ {