diff options
| author | Daniele Varrazzo <daniele.varrazzo@gmail.com> | 2011-11-01 07:09:51 +0000 |
|---|---|---|
| committer | Daniele Varrazzo <daniele.varrazzo@gmail.com> | 2011-11-01 07:09:51 +0000 |
| commit | 00b52c78b32976d1c4c206a43b0cd72e8e21674d (patch) | |
| tree | 95ca9801dc06cf57d185ad60bb6bb218bf748ce0 /doc/src/faq.rst | |
| parent | 572864994404ebb29d6013637a7a03a00cbd68db (diff) | |
| download | psycopg2-00b52c78b32976d1c4c206a43b0cd72e8e21674d.tar.gz | |
Docs cleanup by Josh Kupershmidt
Diffstat (limited to 'doc/src/faq.rst')
| -rw-r--r-- | doc/src/faq.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/faq.rst b/doc/src/faq.rst index e7fe76f..3296cd8 100644 --- a/doc/src/faq.rst +++ b/doc/src/faq.rst @@ -18,7 +18,7 @@ Why does `!psycopg2` leave database sessions "idle in transaction"? :sql:`SELECT`. The transaction is not closed until an explicit `~connection.commit()` or `~connection.rollback()`. - If you are writing a long-living program, you should probably ensure to + If you are writing a long-living program, you should probably make sure to call one of the transaction closing methods before leaving the connection unused for a long time (which may also be a few seconds, depending on the concurrency level in your database). Alternatively you can use a @@ -37,7 +37,7 @@ I receive the error *current transaction is aborted, commands ignored until end Why do I get the error *current transaction is aborted, commands ignored until end of transaction block* when I use `!multiprocessing` (or any other forking system) and not when use `!threading`? Psycopg's connections can't be shared across processes (but are thread - safe). If you are forking the Python process ensure to create a new + safe). If you are forking the Python process make sure to create a new connection in each forked child. See :ref:`thread-safety` for further informations. |