Skip to content
This repository has been archived by the owner on Feb 12, 2022. It is now read-only.

Use server-side connection reset endpoint for pg:killall #1207

Merged
merged 1 commit into from
Sep 17, 2014

Conversation

msakrejda
Copy link
Contributor

This lets users kill all their existing connections even when they
have no remaining connections on their given database plan, preventing
a chicken-and-egg problem in some situations.

This moves a feature that we've been testing in pg-extras into the main toolbelt. The corresponding pg-extras code will be removed.

This lets users kill all their existing connections even when they
have no remaining connections on their given database plan, preventing
a chicken-and-egg problem in some situations.
@jdx
Copy link
Contributor

jdx commented Sep 17, 2014

lgtm

jdx pushed a commit that referenced this pull request Sep 17, 2014
Use server-side connection reset endpoint for pg:killall
@jdx jdx merged commit 44e12e3 into heroku:master Sep 17, 2014
@msakrejda
Copy link
Contributor Author

Thanks! No rush on getting this out.

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

Successfully merging this pull request may close these issues.

2 participants