- Notifications
You must be signed in to change notification settings - Fork328
Activate venv at server start and remove the check from functions#1276
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
| @@ -24,6 +24,7 @@ extension_sql_file!("../sql/schema.sql", name = "schema"); | |||
| #[cfg(not(feature = "use_as_lib"))] | |||
| #[pg_guard] | |||
| pub extern "C" fn _PG_init() { | |||
| bindings::python::activate().expect("Error setting python venv"); | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
This works? I ask because each connection forks from the postmaster. It gets the venv set correctly? :O
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
It works for me locally. I can test from multiple different connections.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Can confirm tested from three different connections and it worked
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Well, that was easy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
🎉
No description provided.