public inbox for [email protected]  

help / color / mirror / Atom feed

From: Stephen Frost <[email protected]>
To: Tom Lane <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: [email protected]
Cc: [email protected]
Subject: Re: Document the limit on the number of parameters
Date: Tue, 7 Aug 2018 23:01:49 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

Greetings Tom,

* Tom Lane ([email protected]) wrote:
> Stephen Frost <[email protected]> writes:
> > * Bruce Momjian ([email protected]) 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 passed 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.

Ah, I read the original poster as saying that it wasn't in the protocol
docs.  If it's there already then I agree, that's sufficient.

Thanks!

Stephen


Attachments:

  [application/pgp-signature] signature.asc (819B, 2-signature.asc)
  download

view thread (5+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Document the limit on the number of parameters
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox