Salesforce Com, Inc.

Serge Philippe Rielau

Rui Zhang

Jeffrey Ira Cohen

Punit B Shah

Rama Krishna Korlapati

Douglas Doole

Randy Philip Spalten

Prashasthi Prabhakar

Jeff Cohen

Mohan Singamshetty

Xiaoyi Tang

John Galloway

Chaoqun Liu

A method for maintaining cache of database objects using a chain set that includes multiple chains each specifying an ordering of database objects is disclosed. In response to a change of state of a particular database object, a corresponding chain is selected. The selected chain is then locked, the state of the particular database object changed, and then the selected chain is unlocked.

Managing objects in shared caches using multiple chains

Techniques are disclosed for handling database queries from multiple different application versions using a single database. A computer system executing a database management system (DBMS) may receive a database query for a database, where the database query is received from a particular version of an application having a plurality of versions. The database query may specify the particular version. The computer system may then identify catalog tables, where the catalog tables include version information columns storing version access information. The computer system may determine that version access information for the database query indicates that one or more database objects corresponding to the database query are accessible to the particular version of the application. Based on the determining, the computer system may access one or more database objects that are responsive to the database query and are accessible to the particular version of the application, which may advantageously reduce or avoid duplication of data stored in the database.

Database implementation for different application versions

Techniques are disclosed relating to concurrently processing transactions. A computer system may maintain a database table having a plurality of versions. Each of the versions may identify a corresponding portion of the database table that transactions associated with that version are permitted to access. The computer system may receive a first request to perform a first transaction to modify a definition of the database table. The computer system may receive a second request to perform a second transaction to modify data stored in the database table. In response to determining that the first and second transactions are associated with different versions of the plurality of versions, the computer system may concurrently process the first and second transactions.

Version-based table locking

Caching runtime plan data that is determined not to change for different invocations of a query plan. In some embodiments, a computing system accesses information that specifies a query plan generated for a first database query and generates a first runtime plan for the first database query based on the query plan. In some embodiments, the system caches information generated for the first runtime plan that is determined not to change for different invocations of the query plan. For example, transformation code may include separate functions for mutable and immutable state. In some embodiments, the system retrieves and uses the cached information to generate a second runtime plan for a second database query. Disclosed techniques may improve performance of query plan transformations that hit in the runtime plan cache.

Caching techniques for query runtime state

A processor can produce a database catalog for a second version of a database management system of the database. The database catalog can store metadata related to definitions of objects or tables included in the second version of the database. A controller can be caused to be established in memory cells being used for the first version of the database. A copy of the database catalog for the second version of the database management system can be stored in the memory cells being used for the first version of the database. The controller, using the copy of the database catalog, can produce the second version of the database management system. The second version of the database management system can be caused to interact with data stored in a storage of the database. The storage can be included in the memory cells being used for the first version of the database.

Growing community of inventors

Alamo, CA, United States of America

Serge Philippe Rielau