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

[Epic] Refactor pgsrv #366

Closed
5 tasks done
greyscaled opened this issue Dec 2, 2022 · 1 comment
Closed
5 tasks done

[Epic] Refactor pgsrv #366

greyscaled opened this issue Dec 2, 2022 · 1 comment
Labels
declined ➖ Declined represents an issue was closed because it was declined epic 🏁 An issue that groups others

Comments

@greyscaled
Copy link
Contributor

greyscaled commented Dec 2, 2022

Description

I'm seeing a trend in a few issues regarding pgsrv, and so I'm taking the liberty to spawn an epic. Essentially, pgsrv is a critical component as without it, nothing in glaredb can be accessed by an external user. The main problems we have are:

Implementing these things should make future implementations in pgsrv easier, and give it access to shared machinery.

Rationale

A hard blocker for beta is terminating ssl in pgsrv. Before we implement that, we want to be confident in the implementation (including tests).

Issues (In an attempted priority order)

@greyscaled
Copy link
Contributor Author

We're not focusing on pgsrv much right now, not doing the sep binary thing - closing epic (but leaving open tickets open)

@greyscaled greyscaled closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2023
@greyscaled greyscaled added the declined ➖ Declined represents an issue was closed because it was declined label Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
declined ➖ Declined represents an issue was closed because it was declined epic 🏁 An issue that groups others
Projects
None yet
Development

No branches or pull requests

1 participant