forked from cockroachdb/cockroach
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
107589: sql: improve query plan for find-running-job-of-type query r=mgartner a=mgartner This commit improves the query plan for the `find-running-jobs-of-type` query by adding a hint to use the `jobs_status_created_idx` and by removing an `ORDER BY` clause if a job ID to ignore was not given. This can eliminate an index join from the query plan in some cases, making the query plan more efficient. Informs cockroachdb#107405 Release note: None 111905: streamingccl: physical replication stream from given timestamp r=adityamaru a=stevendanna This adds a RESUME TIMESTAMP option to CREATE VIRTUAL CLUSTER FROM REPLICATION. When provided, we allow the user to start a replication stream into an _existing_ virtual cluster. When the resume timestamp is provided, the replication stream will be started from that timestamp, with no initial scan. To facilitate this, we add a new argument to crdb_internal.start_replication_stream that allows us to pass a destination-choosen start timestamp. To avoid various catastrophic mistakes, we only allow this when: - The destination tenant must be in service mode None - The provided resume timestamp equals the last recorded "revert timestamp" of the destination tenant. The revert timestamp is set when the tenant has been forcibly reverted to a particular timestamp and is cleared when the tenant is modified in a way that may invalidate a resumption from that timestamp. - If the source tenant has a PreviousSourceTenant set, the new destination must match that previous source tenant field. WARNING: Using this correctly requires that the stream is resumed before garbage collection has progressed past the given resume timestamp. During normal operation, the replication stream maintains a protected timestamp to ensure this is the case. However, when resuming using this new feature, we have no such guarantee. Epic: none Release note: None Co-authored-by: Marcus Gartner <[email protected]> Co-authored-by: Steven Danna <[email protected]>
- Loading branch information
Showing
34 changed files
with
764 additions
and
168 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.