Queries with more than 32k parameters are allowed

version: 8.0.3

As far as I understand, a query can have up to max int16 parameters (from https://www.postgresql.org/docs/devel/protocol-message-formats.html). I found out in my logs error messages like the following.

ERROR:  bind message has 52708 parameter formats but 0 parameters

The means that the prepare message was fine expecting 52708 parameters? and if that’s the case how would that be handled? that takes me the “0 parameters”. I am plainly executing a query, how is it that 0 parameters showed up?

Thank you.

[AlexGalays]

That error message means you’ve got 52708 placeholders, but no values passed in.

The maximum is 65535, which the only way you can hit if you are using it the wrong way. You should be splitting those across queries or hold inside an array, not bundle all into one query. See also here.

That’s not correct.

Currently, there’s an issue where you will see this weird error message even if you pass values and the length of values is exactly the same as the parameter formats. It just throws this error when you’re over 64K parameters.

Tested just now:

There’s always 4 columns worth of parameters per row (So ($1, $2, $3, $4) is the first row). Turns out the number in the error message is by how much you exceed the 64K limit; it seems the rest gets dropped but it results in a hard to understand error message.

112720 parameters/values;  bind message has 47184 parameter formats but 0 parameters

94896 parameters/values;  bind message has 29360 parameter formats but 0 parameters

91488 parameters/values;  bind message has 25952 parameter formats but 0 parameters

77616 parameters/values;  bind message has 12080 parameter formats but 0 parameters

66936 parameters/values;  bind message has 1400 parameter formats but 0 parameters

43824 parameters/values => works fine.

Surely the error message could be more helpful in tracing back to the actual problem?

[vitaly-t]

That error message means you’ve got 52708 placeholders, but no values passed in.

The maximum is 65535, which the only way you can hit if you are using it the wrong way. You should be splitting those across queries or hold inside an array, not bundle all into one query. See also here.