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

Abort operations on request abort #176

Open
strk opened this issue Mar 20, 2014 · 2 comments
Open

Abort operations on request abort #176

strk opened this issue Mar 20, 2014 · 2 comments

Comments

@strk
Copy link
Contributor

strk commented Mar 20, 2014

When client aborts the connection we want to stop doing our work.
See #76

@rochoa
Copy link
Contributor

rochoa commented Jun 10, 2014

What do you mean by "stop doing our work"?

I guess one of the things you propose is to cancel queries to postgres (specially the ones going through mapnik). What else?

@strk
Copy link
Contributor Author

strk commented Jun 10, 2014

Those going trough mapnik, those going directly though the PSQL module. An any work which is outside of PostgreSQL (like formatting outputs). The more we stop doing the better.

Not waiting for responses from abort requests might be a good idea (I'm thinking about clients that abort due to client timeout and any of our database interactions, including cancels, queued in pgbouncer due to a backend crash...)

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

No branches or pull requests

2 participants