timer database - Search results in mailing lists
Mailing lists >> psycopg >> Thread
2024-09-07 18:48:01 | psycopg2: proper positioning of .commit() within try: except: blocks (Karsten Hilbert)
database. If it fails, no worries, the supplied default is used by follow-on code and storing it is re-tried next time
Mailing lists >> psycopg >> Thread
2024-02-16 05:45:15 | Re: Reporting UnicodeEncodeError info on arbitrary data sent to PG with psycopg3 (Karl O. Pinc)
time, when you bought a computer it came with only one set of characters and only one way to represent, encode, each of those characters into exactly one byte. These days life
Mailing lists >> psycopg >> Thread
2023-04-24 21:16:42 | Re: Consecutive Inserts Freeze Execution of Psycopg3 (Michael P. McDonnell)
database issue as a whole that I'm just now tracking down. Just thought you'd like to know that it was not a psycopg(3 or 2) issue, not a sqlalchemy issue
Mailing lists >> psycopg >> Thread
2022-10-17 11:25:14 | Puzzling situation with threads and psycopg2 on RDS (Stefan Knecht)
time: 0:00:00.021 user=postgres database=postgres host=10.0.1.17 port=36356 2022-10-17 10:59:03 UTC:10.0.1.17(36350):postgres
Mailing lists >> psycopg >> Thread
2021-02-04 16:55:21 | Latest developments in psycopg3 (Daniele Varrazzo)
time, in order to accommodate some of these quirks, there were special cases in the adaptation functions, but now there is a generic mechanism which can be used for these Python types whose Postgres type
Mailing lists >> psycopg >> Thread
2021-01-18 14:29:34 | Re: Designing a better connection pool for psycopg3 (Daniele Varrazzo)
database anymore. This node is arguably broken. If the reconnection thread fails to obtain new connections, and the ones currently in the pool are discarded as detected broken, eventually the pool is depleted. The requesting
Mailing lists >> psycopg >> Thread >> Search in thread (2)
2020-11-09 02:19:04 | Re: psycopg3 and adaptation choices (Vladimir Ryabtsev)
database world? '%s' feels like old-school string formatting, new server-side parameter binding may want to give some new impression. Moreover, it appears more convenient when you have parameters numbered and can reuse them
Mailing lists >> psycopg >> Thread
2020-03-06 10:31:39 | psycopg3: request for support (Daniele Varrazzo)
time to write psycopg3... if only I didn't have that background fear and need for stability that is screaming that I cannot enjoy the simple things of life (playing ukulele, making photography, writing database
Mailing lists >> psycopg >> Thread
2020-01-15 06:36:26 | Executing stored procs (Anthony Waye)
database_name, host=args.redshift_address, port=args.redshift_port, user=redshift_creds['username'], password=redshift_creds['password']) except Exception as e: raise(e) rand = random.randrange( 15, 45) timestamp = datetime.utcnow().strftime
Mailing lists >> psycopg >> Thread
2019-04-04 13:05:52 | Psycopg 2.8 released (Daniele Varrazzo)
databases with mixed encodings on Python 3 (ticket #835). - Added 'table_oid' and 'table_column' attributes on 'cursor.description' items (ticket #661). - Added 'connection.info' object to retrieve various PostgreSQL connection information (ticket #726). - Added
Mailing lists >> psycopg >> Thread
2018-10-04 12:32:35 | Re: Integration of Psycopg with XTA (Federico Di Gregorio)
into the database all the time when do you expect to look at it? -- Charlie Clark
Mailing lists >> psycopg >> Thread
2018-07-19 13:05:45 | R: Number of SQL queries (Federico Di Gregorio)
database connection is used multiple times. So no, you cant use psycopg to count the number
Mailing lists >> psycopg >> Thread
2017-12-05 21:31:32 | LISTEN, select/poll question/clarification (Israel Brewster)
time between poll() ing the database for new NOTIFYs, but apparently that's not working
Mailing lists >> psycopg >> Thread >> Search in thread (4)
2017-08-04 00:08:18 | Re: [psycopg] Changing set_session implementation (Karsten Hilbert)
database gnumed_v20_copy template gnumed_v20 2017-08-03 21:00:19 GMT LOG: 00000: disconnection: session time
Mailing lists >> psycopg >> Thread
2017-08-03 10:00:56 | [psycopg] Feature Request: [PostgreSQL 10] Support for preparing the encrypted password (Ashesh Vashi)
database server (done by the 'PQencryptPasswordConn' internally). For PostgreSQL <= 9.6, it will always use the 'PQencryptPassword' function of libpq, and ignores the algorithm. For PostgreSQL 10+, it depends on the libpq version used at compile