We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
You can't create columnstore tables with the following constraints: UNIQUE PRIMARY KEY FOREIGN KEY
UNIQUE PRIMARY KEY FOREIGN KEY
The text was updated successfully, but these errors were encountered:
It would be really really really good to have this. One of the 2 things that keep us from using pg_mooncake
Sorry, something went wrong.
Hey @dpxcc is someone looking at this ? Can I start with this one?
Hey @ritwizsinha, we still need to finalize the design for this one. Our initial idea is to use a 2-layer index approach: build index for each data file, and then build speedy lookup layer on top across multiple data files, similar to what we did back in SingleStore [1] https://dl.acm.org/doi/pdf/10.1145/3514221.3526055 [2] https://cs.purdue.edu/homes/csjgwang/pubs/VLDB24_SingleStoreVec.pdf
No branches or pull requests
You can't create columnstore tables with the following constraints:
UNIQUE PRIMARY KEY FOREIGN KEY
The text was updated successfully, but these errors were encountered: