-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hasura fails because max_function_args in postgres is no enough #10227
Comments
Any help?? Citus is not usable with hasura because of this error |
Is there a way to configure hasura to use not json_(..,..,..,,) witha lot of arguments but use maybe json_array not json_object which causes this problem |
More context about the issue I also fount heer https://postgrespro.com/list/thread-id/2486891 |
If i use in my databases.yaml kind: postgres kind: citus |
+1 This is supper needed and is a limitation from Hasura Big companies do not use just postgres since it doesn't make sense in big apps but with some extension like Citus |
Can you explain how you trigger this issue? Is it a problem when loading metadata, making a query, using the Console, or something else? There aren't that many differences between the vanilla PostgreSQL and Citus backends, so I am surprised that switching the "kind" would help, but that does narrow it down a lot. I would also recommend checking out Hasura DDN, which fixes many of the issues in Hasura GraphQL Engine v2. Most notably in this case, the custom Citus support is strictly limited to introspection, and during queries, both PostgreSQL and Citus are treated identically. |
This is a problem when running a simple get query for example to get a row from such a table cc @SamirTalwar |
I saw @ammirator-administrator's comments in #10229 pointing to a code location. That code is specific to subscriptions, not queries, and is not specific to Citus; it is the same code for all backends based on PostgreSQL. Is it possible that in testing, you made a subscription to Citus, but a query to vanilla PostgreSQL? That would explain the discrepancy. |
Hey @SamirTalwar The problem I have is in Queries, just by runing a graphql query for example get app_config_by_pk (Which is a table with more than 50columns it returns teh error) |
Version Information
Server Version:
2.36.1
Environment
OSS
What is the current behaviour?
Hasura fails to retrieve data from a Table (From Citus), and that happens because it seems that max_function_args in PG is not enough for that, the table indeed has let's say 50columns, but I do not understand why hasura creates a Method with more than max_function_args and try to retrieve data after that
That may be due to json modules used in hasura or something like that
And to fix that you just hae to recompile PF to give a bigger max_function_args and that is not possible in most cases since no one wants to recompile PG) this value cantbe added to PG cofig it is a readonly value and postgres doesnt allow that
SO it seems that tables with more that 50columns are not supported in hasura at the mooment
This is the errror
The text was updated successfully, but these errors were encountered: