Elvis Pranskevichus

@1st1, @jaclarke any update here?

> This would verify that the input is a valid identifier with a regex. Pretty much any Unicode string is a valid identifier as long as you quote it. The...

Not bad! Though keep in mind that neither EdgeDB nor asyncpg have native macOS arm64 builds yet, so there's probably some emulation overhead, especially for EdgeDB. Would be interesting to...

> The problem here is that asyncpg doesn't explicitly close portals when it's done using them asyncpg uses an unnamed portal in `fetch` and other methods. Postgres does not require...

> But what about cursors, which are connected to portals (different from prepared statements)? They also get closed on garbage collection. We can implement an explicit `.close()` method, though.

> doesn't that mean we never actually explicitly close any portals? Hmm, you're right, this could be an issue.

I don't recognize that error. Are you running vanilla Postgres?

Also, you probably meant this (your column is a timetstamp, not a date): ```python await conn.set_type_codec( typename='timestamptz', encoder=str, decoder=str, schema='pg_catalog', format='text' ) ```

This is because ltree doesn't support binary I/O, and asyncpg doesn't implement text I/O for composite types, so there isn't much we can do here unfortunately.

Composite types are normally handled automatically, since their (binary) structure is well defined. The issue in this case is that AgensGraph chose to put their extension types into the standard...