From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
cc: Bruce Momjian <bruce@momjian.us>, postgres@kellerer.name,
        pgsql-docs@lists.postgresql.org
Subject: Re: Document the limit on the number of parameters
In-reply-to: <20180808020655.GC27724@tamriel.snowman.net>
References: <153183390829.1395.16339447781418953738@wrigleys.postgresql.org>
 <20180807215822.GM7297@momjian.us>
 <20180808020655.GC27724@tamriel.snowman.net>
Comments: In-reply-to Stephen Frost <sfrost@snowman.net>
	message dated "Tue, 07 Aug 2018 22:06:55 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <13393.1533697144.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 07 Aug 2018 22:59:04 -0400
Message-ID: <13394.1533697144@sss.pgh.pa.us>
Precedence: bulk

Stephen Frost <sfrost@snowman.net> writes:
> * Bruce Momjian (bruce@momjian.us) wrote:
>> On Tue, Jul 17, 2018 at 01:25:08PM +0000, PG Doc comments form wrote:
>>> The backend protocol limits the number of parameters that can be passe=
d for
>>> a prepared statement to 32767 (2 byte signed integer).

>> Uh, is this something people will care about?

> Seems like a limitation in the backend protocol should probably be
> documented in the backend protocol section of the docs..

It is: the definition of the Bind message format says that the parameter
count is an int16.

The question is whether this deserves to be cross-referenced from
elsewhere.  I agree with Bruce that it seems unlikely to be helpful.

			regards, tom lane