Snowflake Inc.

Krishna B Nibhanupudi

Fabio Angius

Zechao Shang

Sahaj Saini

Lin Chan

Sarvesh Singh

Techniques for constructing transaction lock wait history showing blocker queries are described. A first transaction referencing a resource saved in a network-based data warehouse is received where the first transaction being blocked due to second transaction accessing the resource. A first telemetry event based on the first transaction being blocked is transmitted. After acquiring lock ownership of the resource by the first transaction, a second telemetry event based on acquiring lock ownership by the first transaction is transmitted.

Event driven technique for constructing transaction lock wait history

The subject technology sends a first statement to an execution node for executing the first statement on first storage using micro-partitions. The subject technology sends a second statement to the execution node for executing the second statement on linearizable storage. The subject technology sends a request to prepare a commit of a cross domain transaction associated with the first statement and the second statement. The subject technology generates a new version of a set of tables that were modified by the cross domain transaction and updating first metadata in a metadata database to indicate the new version. The subject technology finalizes the commit of the cross domain transaction and updates second metadata that the cross domain transaction has been committed.

Database transactions across different domains

The subject technology receives a cross domain transaction, the cross domain transaction including a plurality of statements. The subject technology sends a first statement to an execution node for executing the first statement on first storage using micro-partitions. The subject technology sends a second statement to the execution node for executing the second statement on linearizable storage. The subject technology updates, using a metadata database, a status of the cross domain transaction to a pre-commit state. The subject technology sends a request to prepare a commit of the cross domain transaction. The subject technology updates, using the metadata database, the status of the cross domain transaction to a committing state. The subject technology finalizes the commit of the cross domain transaction and updating second metadata that the cross domain transaction has been committed.

Growing community of inventors

Shoreline, WA, United States of America

Krishna B Nibhanupudi