"cannot pass more than 100 arguments" error with actor.org_unit_ancestor_setting_batch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
High
|
Unassigned |
Bug Description
Evergreen 2.10
Postgres 9.1+ (confirmed on 9.4)
A new actor.org_
The maximum number of arguments allowed by a Postgres server is determined at build time by the value of the FUNC_MAX_ARGS parameter, which defaults to 100 -- see the entry for max_function_args on this page:
http://
I imagine all packaged versions of PG just use the default value. We probably want to figure out a way to pass the list of org setting names as a single parameter, rather than as an indefinitely large number of separate values.
Changed in evergreen: | |
status: | New → Confirmed |
milestone: | none → 2.10.2 |
importance: | Undecided → High |
tags: | added: regression |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
The stored procedure is called from only one place, OpenILS: :Application: :AppUtils- >ou_ancestor_ setting_ batch_insecure( ), so one solution would be to have that caller split up invocations of the stored procedure. It would be a good idea to measure execution time to compare that approach with marshaling the list of OU names into a single string to pass to the stored procedure.