Thread: Re: problem to developing the lock

Re: problem to developing the lock

From
"frank_lupo"
Date:
> It's rumoured that frank_lupo once said:
> > I am developing the lock but I find problems why the pgadmin2 it
> > remains blocked.  How can be resolved the problem?
> 
> > Read mail:
> > drop view not possible to select from pg_view
> > http://archives.postgresql.org/pgsql-general/2003-01/msg01031.php
> 
> Sorry Frank, I don't understand what you mean :-(
> 
> Regards, Dave.
> 
> 
> 

I set autocommit =off. 
When drop view and i do not send commit or rollback,is not possible to select from other user on pg_view. The Pgadmin2
whenread schema is locked,and is not possible to make whichever other operation.  This is my problem.
 
It is not possible to use pgadmin2 if the view are locked.


Bye !!
Frank Lupo (Wolf) !!

   /\_ _/\
   \ o o /
--ooo-----ooo---



--
Prendi GRATIS l'email universale che... risparmia: http://www.email.it/f

Sponsor:
Un giorno a settimana gusta la Mozzarella di Bufala Campana e la Treccia di Agerola.
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=982&d=22-2


Re: problem to developing the lock

From
"Dave Page"
Date:
It's rumoured that frank_lupo once said:

> I set autocommit =off.
> When drop view and i do not send commit or rollback,is not possible to
> select from other user on pg_view. The Pgadmin2 when read schema is
> locked,and is not possible to make whichever other operation.  This is
> my problem.
 It is not possible to use pgadmin2 if the view are
> locked.

Oh, I see. How about wrapping everything in a transaction in
pgDatabase.Execute in pgSchema? We should probably then provide a
secondary connection for use with SQL queries in pgAdmin. Probably not a
bad idea anyway.
What do you think?

Regards, Dave.