fix: Drop include clause from list tables#13332
Merged
kodiakhq[bot] merged 3 commits intoAug 28, 2023
Merged
Conversation
hermanschaaf
approved these changes
Aug 28, 2023
Contributor
|
Looks good, though I don't know if this should be marked as a |
candiduslynx
approved these changes
Aug 28, 2023
Co-authored-by: Alex Shcherbakov <candiduslynx@users.noreply.github.com>
Member
Author
Yeah, I'm not sure. It shouldn't have any user facing impact, but maybe I'll do a |
kodiakhq Bot
pushed a commit
that referenced
this pull request
Aug 29, 2023
🤖 I have created a release *beep* *boop* --- ## [6.0.1](plugins-destination-postgresql-v6.0.0...plugins-destination-postgresql-v6.0.1) (2023-08-29) ### Bug Fixes * **deps:** Update `github.com/cloudquery/arrow/go/v13` to `github.com/apache/arrow/go/v14` ([#13341](#13341)) ([feb8f87](feb8f87)) * **deps:** Update module github.com/cloudquery/plugin-sdk/v4 to v4.5.6 ([#13345](#13345)) ([a995a05](a995a05)) * Drop include clause from list tables ([#13332](#13332)) ([7b6369e](7b6369e)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
hermanschaaf
pushed a commit
that referenced
this pull request
Aug 29, 2023
#### Summary Follow up to #13331. On AWS this means we search an array of ~600 items. Since at the moment we only have a single `MigrateTableBatch` call for all the tables, no point of having the `WHERE` clause (and even with multiple migrate batches might be faster just to query everything). See also https://www.postgresql.org/docs/current/arrays.html:  We can't really follow that tip though <!--
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow up to #13331.
On AWS this means we search an array of ~600 items. Since at the moment we only have a single
MigrateTableBatchcall for all the tables, no point of having theWHEREclause (and even with multiple migrate batches might be faster just to query everything).See also https://www.postgresql.org/docs/current/arrays.html:
We can't really follow that tip though