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

[COR-842] Spike: Determine what it means to certify an extension #112

Open
coredb-service-user opened this issue May 16, 2023 · 1 comment
Labels
Medium priority Created by Linear-GitHub Sync oss-trunk Created by Linear-GitHub Sync

Comments

@coredb-service-user
Copy link

Implement a system for 'certifying' Postgres extensions. This will likely involve some spike time as we think about what makes an extension 'certified'.

From SyncLinear.com | COR-842

@coredb-service-user coredb-service-user added general availability Created by Linear-GitHub Sync oss-trunk Created by Linear-GitHub Sync labels May 16, 2023
@coredb-service-user coredb-service-user changed the title [COR-842] Extension Certification [COR-842] Spike: Determine what it means to certify an extension May 24, 2023
@ianstanton ianstanton added the Medium priority Created by Linear-GitHub Sync label May 25, 2023
@coredb-service-user coredb-service-user added 1.0 GA Created by Linear-GitHub Sync and removed general availability Created by Linear-GitHub Sync 1.0 GA Created by Linear-GitHub Sync labels May 26, 2023
@coredb-service-user
Copy link
Author

Samay mentioned:

As we move towards certification of extensions, we should also run the entire Postgres core test suite with extension binary installed to make sure it doesn’t mess anything up in core Postgres functionality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Medium priority Created by Linear-GitHub Sync oss-trunk Created by Linear-GitHub Sync
Projects
None yet
Development

No branches or pull requests

2 participants