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

API design decision: Naming #2

Open
JelteF opened this issue May 27, 2024 · 1 comment
Open

API design decision: Naming #2

JelteF opened this issue May 27, 2024 · 1 comment
Milestone

Comments

@JelteF
Copy link
Member

JelteF commented May 27, 2024

Do we want:

CREATE EXTENSION pgbouncer;

or

CREATE EXTENSION pg_pgbouncer;

What about GUCs and the schema. Should they be pgbouncer.some_table or pg_pgbouncer.sometable.

Changing the extension name completely to something else, would also be acceptable to me.

@JelteF JelteF added this to the First release milestone May 28, 2024
emelsimsek pushed a commit that referenced this issue May 28, 2024
…48-d3f5-4805-9ec0-094c0d8f0a59

Adding Microsoft SECURITY.MD
@petere
Copy link
Member

petere commented Jun 2, 2024

Let's use pg_pgbouncer consistently as the extension name and namespace for this. Otherwise it would be confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants