Functions

The SQL_STATEMENT_NOT_YET_COMPLETE error will surface if we query a view in Materialize before data exists for that view. It is common to hit this error just after creating a view, particularly in testing or demo code.

Create and return a new PostgreSQL client, spawning off the connection object along the way.

delay_for 🔒

Limit the queries per second against a view in Materialize.

Delete an index

Delete a source and all dependent views, if the source exists

Delete a table and all dependent views, if the table exists

Run PostgreSQL’s execute function

Run Materialize’s SHOW SOURCES command

Try running PostgresSQL’s query function, checking for a common Materialize error in check_error.

Try running PostgreSQL’s query_one function, checking for a common Materialize error in check_error.