Tirumarai Selvan

> The problem that's probably causing the deadlocks is that the ALTER TABLE statement in the migration query touches every row of the table, which locks until complete. The subscription...

> Still curious about the select * from table behaviour, isn't this suboptimal in the amount of data that is being fetched? If you look further into the generated query,...

There are couple of architectural complexities involved with this capability: 1. Enum types can come from remote schemas which have permissions 2. Enum types from Postgres do not have permissions...

@0x777 Any updates here?

FYI, the array value can be sent as [Postgres array literal](https://www.postgresql.org/docs/current/arrays.html) which looks like ` "x-hasura-array-val": "{t1,t2,t3}"`. This issue is for supporting the format `[t1,t2,t3]`.

@hthillman Does the table here help? https://hasura.io/docs/1.0/graphql/core/api-reference/postgresql-types.html#introduction

@hthillman That's right! Although "Hasura Int" is standard Graphql scalar Int: https://spec.graphql.org/June2018/#sec-Int The current issue is for supporting `limit`'s type as bigint (but that seems like a breaking change, unfortunately)

> I've also raised the issue with Heroku directly -- since I don't believe CREATE EXTENSION IF NOT EXISTS pgcrypto SCHEMA public should fail if its already available on the...

FYI, we are working on adding the ability to add "extensions_schema" when adding a PG source so you can explicitly specify the schema where pgcrypto should be installed on the...

Hey folks, this has been fixed as of v2.11.0-beta.1 . There are 2 places where pgrcypto is required: in metadata db and source db (only if using event triggers) If...