Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ysql: transparently change gin to ybgin #8402

Closed
jaki opened this issue May 12, 2021 · 0 comments
Closed

ysql: transparently change gin to ybgin #8402

jaki opened this issue May 12, 2021 · 0 comments
Assignees
Labels
area/ysql Yugabyte SQL (YSQL) kind/enhancement This is an enhancement of an existing feature

Comments

@jaki
Copy link
Contributor

jaki commented May 12, 2021

For yugabyte relations, transparently change gin access method to ybgin access method (once ybgin access method is created). We already do this for btree/hash to lsm.

@jaki jaki added kind/enhancement This is an enhancement of an existing feature area/ysql Yugabyte SQL (YSQL) labels May 12, 2021
@jaki jaki self-assigned this May 12, 2021
@jaki jaki mentioned this issue Sep 9, 2021
26 tasks
@jaki jaki closed this as completed in 4ae9e7d Sep 9, 2021
jaki added a commit that referenced this issue Sep 9, 2021
Summary:
Landed D11572 (commit 4ae9e7d) too
hastily, and missed some test failures introduced over rebase. Fix those
test failures.

Test Plan:
Jenkins: urgent

    #!/usr/bin/env bash
    # yb_pg_tsearch
    ./yb_build.sh --java-test org.yb.pgsql.TestPgRegressTypesString
    # yb_pg_hstore
    ./yb_build.sh --java-test org.yb.pgsql.TestPgRegressContribHstore
    # yb_pg__int
    ./yb_build.sh --java-test  org.yb.pgsql.TestPgRegressContribIntarray

Reviewers: zyu

Reviewed By: zyu

Subscribers: yql

Differential Revision: https://phabricator.dev.yugabyte.com/D12953
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ysql Yugabyte SQL (YSQL) kind/enhancement This is an enhancement of an existing feature
Projects
None yet
Development

No branches or pull requests

1 participant