| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Richard Michael <rmichael(at)edgeofthenet(dot)org> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Slow ext'd query via client native implementation vs. libpq & simple psql |
| Date: | 2020-03-12 20:43:36 |
| Message-ID: | 20200312204336.GE29065@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Mar 12, 2020 at 04:27:54PM -0400, Richard Michael wrote:
> > psql can't do it, but pygres can do it since last year.
>
> Thank you for mentioning it. Do you mean this:
> https://github.com/rogamba/pygres ?
Ugh, no. I'm referring to PyGreSQL, which was at one point a part of the
postgres source tree.
https://www.pygresql.org/
$ python -c "import pg; print(pg.DB('postgres').query('SELECT 1').getresult())"
[(1,)]
$ python -c "import pg; p=pg.DB('postgres'); p.prepare('q', 'SELECT 1'); print(p.query_prepared('q').getresult())"
[(1,)]
--
Justin
(I'm having trouble believe someone made a project called "pygres", which uses
python, postgres, and psycopg... Will mail D'Arcy)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anders Steinlein | 2020-03-21 12:02:10 | Slow planning time when public schema included (12 vs. 9.4) |
| Previous Message | Tom Lane | 2020-03-11 22:54:16 | Re: Slow ext'd query via client native implementation vs. libpq & simple psql |