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

Support target session attrs #810

Closed
wants to merge 1 commit into from

Conversation

bpicolo
Copy link

@bpicolo bpicolo commented Nov 21, 2018

This is a remake of #714 that pulls in much related code, but also has a couple bugfixes for SSL tests, and updates some related documentation (for how to run multi-pg tests locally).

@bpicolo bpicolo force-pushed the support_target_session_attrs branch 4 times, most recently from c68363e to 20c8b4d Compare November 21, 2018 19:22
@bpicolo bpicolo force-pushed the support_target_session_attrs branch from 20c8b4d to 43cf9fb Compare November 26, 2018 19:48
@bpicolo bpicolo closed this Nov 26, 2018
@bpicolo bpicolo reopened this Nov 26, 2018
panicking = false
return cn, err

// In most cases
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgot to finish this sentence.

There's some question about how we would want to return errors/ connections here. Currently this takes the path of least resistance and uses the latest connection / err

@costela
Copy link

costela commented Nov 27, 2018

Maybe I'm missing something, but why couldn't this have been done as an improvement to #714? Seems a bit impolite to take my initial code and just squash it under your name.

@bpicolo
Copy link
Author

bpicolo commented Nov 27, 2018

@costela probably should be! Happy to close this. I needed it myself and am not used to PRing other people’s forked PRs and GitHub doesn’t provide the best social interactivity there =]. Happy to figure out how to integrate / close this with you. Definitely appreciate the work you put in.

Didn’t intend to ignore the work you put in, which is why I linked your PR in the initial comment. Sorry that I didn’t do the best job there. Getting the maintainer notion of “I don’t plan to look at this any time soon” put me in a pickle of needing to pull things out

I actually hadn’t really intended to put this PR in the main repo at all, but sort of just edited the comment after I’d noticed I unintentionally had

@bpicolo bpicolo closed this Nov 27, 2018
@costela
Copy link

costela commented Nov 29, 2018

Sure, totally understandable. Thanks for the clarification!
I'd suggest the following: open PRs for your improvements against my fork and I'll rebase the original PR with your additional commits. This way we can work together on keeping this fork relatively up-to-date against the original repo.

And if it turns out we have fundamentally different ideas about how this feature should work, you can always open a separate PR in the future again.

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

Successfully merging this pull request may close these issues.

2 participants