On Thursday 10 February 2005 08:56 pm, Alex Turner wrote:
Just a small warning for those people using python with postgresql:
pysgresql and psycopg are very different animals. You cannot drop in
one as a replacement for the other, even though both 'claim' to be DB
API 2.0 compliant.
None of
Funny you should say that - the system I am developing has a similar
system, although not as fully developed. I am now having trouble with
psycopg locking up my database somehow. It's almost like there are
outstanding locks on objects in the database that are preventing other
threads operating.
On Fri, Feb 11, 2005 at 04:05:03PM -0500, Alex Turner wrote:
I am now having trouble with psycopg locking up my database somehow.
It's almost like there are outstanding locks on objects in the database
that are preventing other threads operating.
Do you mean the Python script itself is locked
What does the column 'relation' in pg_locks key to (Is there any docs
on the website for this?)
Alex
On Fri, 11 Feb 2005 14:20:32 -0700, Michael Fuhr [EMAIL PROTECTED] wrote:
On Fri, Feb 11, 2005 at 04:05:03PM -0500, Alex Turner wrote:
I am now having trouble with psycopg locking up my
pg_locks - awesome - I will check it out...
I think it's uncommitted transactions that are causing the problem.
The original code was written very transactionaly.
Alex Turner
netEconomist
On Fri, 11 Feb 2005 14:20:32 -0700, Michael Fuhr [EMAIL PROTECTED] wrote:
On Fri, Feb 11, 2005 at
On Fri, Feb 11, 2005 at 04:24:17PM -0500, Alex Turner wrote:
pg_locks - awesome - I will check it out...
See also pg_stat_activity. If you don't see anything in the
current_query column then edit postgresql.conf and set
stats_command_string = true, then restart the database. With
this
On Fri, Feb 11, 2005 at 04:26:04PM -0500, Alex Turner wrote:
What does the column 'relation' in pg_locks key to (Is there any docs
on the website for this?)
See the System Catalogs chapter in the documentation (substitute
your version of PostgreSQL in the link):
Just a small warning for those people using python with postgresql:
pysgresql and psycopg are very different animals. You cannot drop in
one as a replacement for the other, even though both 'claim' to be DB
API 2.0 compliant. If you are starting out with python on postgresql,
I would strongly
