Skip to content

[question] PostgreSQL 11 compatibility #379

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

Closed
eirnym opened this issue Oct 22, 2018 · 2 comments
Closed

[question] PostgreSQL 11 compatibility #379

eirnym opened this issue Oct 22, 2018 · 2 comments

Comments

@eirnym
Copy link

eirnym commented Oct 22, 2018

I want to know if most resent release of asyncpg is compatible with PostgreSQL 11. If yes, I want to see it in README and documentation.

It's ok if I need to rebuild this package.

  • asyncpg version: 0.17.0
  • PostgreSQL version: 11.0
  • Do you use a PostgreSQL SaaS? If so, which? Can you reproduce
    the issue with a local PostgreSQL install?
    : local installation
  • Python version: 3.7
  • Platform: macOS (from MacPorts) / Fedora 28 (builds from PostgreSQL.org)
  • Do you use pgbouncer?: no
  • Did you install asyncpg with pip?: yes
  • If you built asyncpg locally, which version of Cython did you use?: 0.28.5
  • Can the issue be reproduced under both asyncio and
    uvloop?
    : I use uvloop
@elprans
Copy link
Member

elprans commented Oct 22, 2018

The tests are passing (barring one edge-case), so you should be good to go. We will declare official support with the next release.

elprans added a commit that referenced this issue Oct 22, 2018
@eirnym
Copy link
Author

eirnym commented Oct 23, 2018

Sounds good for me, will wait for it.

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

No branches or pull requests

2 participants