On Saturday 19 December 2009 12:45:15 pm Clayton Graf wrote:
> I think I got it...
>
> I was just using
>
> select * from table1;
> select * from table2;
> select * from tablen;
>
> instead of
>
> begin;
> select * from table1;
> select * from table2;
> select * from tablen;
> commit;
>
> Using MS-
I think I got it...
I was just using
select * from table1;
select * from table2;
select * from tablen;
instead of
begin;
select * from table1;
select * from table2;
select * from tablen;
commit;
Using MS-SQLSERVER the begin trans is "implicit" at first update or delete
command. It is not neces
On Sat, Dec 19, 2009 at 10:58 AM, Clayton Graf wrote:
> Ok, but this is really my problem: I cannot perform an ALTER TABLE with the
> system in production mode, because the ALTER TABLE hangs due an
> AccessShareLock.
until the lock is released, are your selects all that long?
besides, why are you
Ok, but this is really my problem: I cannot perform an ALTER TABLE with the
system in production mode, because the ALTER TABLE hangs due an
AccessShareLock.
We use two-tier mode, so is it necessary to shutdown all users before
perform an ALTER TABLE? Is it this true?
Thanks,
Clayton
2009/12/19
On Sat, Dec 19, 2009 at 9:04 AM, Clayton Graf wrote:
> I get an AccessShareLock in a simple select command and I am not using the
> FOR SHARE clause.
http://www.postgresql.org/docs/current/static/explicit-locking.html says:
"""
ACCESS SHARE
Conflicts with the ACCESS EXCLUSIVE lock mode only.
I get an AccessShareLock in a simple select command and I am not using the
FOR SHARE clause.
The select is just "select * from controle". The connection is JDBC and the
driver is postgresql-8.4-701.jar.
What am I doing wrong?
This is the code:
Class.forName(jdbc).newInstance();
