timer choosing - Search results in mailing lists
Mailing lists >> psycopg >> Thread
2021-02-04 16:55:21 | Latest developments in psycopg3 (Daniele Varrazzo)
choose if %s is a number or an interval. Other thorny problems are with arrays: you know that in Python there are lists of any types (we hope they are uniform here) and in Postgres
Mailing lists >> psycopg >> Thread
2021-01-18 18:20:12 | Re: Designing a better connection pool for psycopg3 (Vladimir Ryabtsev)
choose whatever is better for your implementation. And yes, stack looks reasonable. Many services and applications do not really need many connections but would like to benefit from automatic reconnections. So the default is questionable
Mailing lists >> psycopg >> Thread
2019-06-14 00:05:18 | psycopg 2.8.3 released (Daniele Varrazzo)
Choosing the right frequency to send replication feedback messages from the client to the server was previously the developer's responsibility, with too many feedback messages being a waste of bandwidth and server resources
Mailing lists >> psycopg >> Thread
2016-02-05 07:45:06 | Re: A PGsendQuery API design for your review (Karl O. Pinc)
time. From another standpoint though, no. I don't understand at all. Why should psycopg2 be passing judgment on what user interface is appropriate for interacting with a PG database? It's fine to reject
Mailing lists >> psycopg >> Thread
2012-09-24 08:56:38 | Range type adaptation implemented (Daniele Varrazzo)
choose whether we want an int4range or an int8range, and Postgres won't forgive the error with a cast. The shortcoming of using a literal is that in case of ambiguity postgres will refuse
Mailing lists >> psycopg >> Thread
2012-03-25 12:15:17 | Re: Connection function (Bill House)
times one will not be selecting all the records in a table, so this function can be expanded to include a parameter for the selection criteria so that that identical criteria may be used again
Mailing lists >> psycopg >> Thread
2011-01-13 12:37:56 | Proposal: efficient iter on named cursors (Daniele Varrazzo)
time overhead in case of large recordsets (exactly the ones you may want to retrieve with a named cursors...) Currently the most efficient way to iterate on a named cursor is something like: nrecs