Support AsyncPG

[p-null]

Jira Link: DB-1359
Hi,

I am using asyncpg as database driver for my python application.

Currently, it will break on split_server_version_string() in asyncpg library: inside that function it will get version_string, and convert each part of that string to int. While YugabyteDB returns the version_string containing strings that cant be converted to int. In my case, it's '11.2-YB-2.2.0.0-b0'

A minimum example to reproduce:

import asyncio
import asyncpg

async def run():
    conn = await asyncpg.connect(user='1234',
                                 password='1234',
                                 database='1234',
                                 host='1234,
                                 port=1234)
    values = await conn.execute('''SELECT name, age, language FROM employee WHERE id = 1''')
    print(values)
    await conn.close()

loop = asyncio.get_event_loop()
loop.run_until_complete(run())

[p-null]

The purpose of this function( get_server_version) is to get the version of PostgreSQL server originally. It will let asyncpg choose the appropriate driver to connect with PostgreSQL server.

So here I think the purpose is to get YugabyteDB's PosrgreSQL version, like which version of PostgreSQL that YB is using.

[tedyu]

Within '11.2-YB-2.2.0.0-b0', the 11.2 is the corresponding Postgres version.

[stevebang]

See related blog post: 1M rows/s from Postgres to Python

[andyondrya]

Hey there. Something up to date on this thread, I'm having the same issue with Yugabyte running on a kubernetes cluster, would I define it something like this?

conn = await asyncpg.connect(user='1234',
                                 password='1234',
                                 database='1234',
                                 host='1234,
                                 port=1234)
conn = conn.get_server_version()```

[sycured]

Have you any fix?

[andyondrya]

I kinda figured out the issue when I rebuilt the wheel after editing serverversion.py