On Thu, Oct 13, 2005 at 08:32:28AM +, Carlos Benkendorf wrote:
> I agree that select for update will be the best choice but it
> does not have any effect with insert statements.
>
> if you try the following sequence in two different transactions,
> the select for update will succeed but the i
I agree that select for update will be the best choice but it does not have any effect with insert statements.
if you try the following sequence in two different transactions, the select for update will succeed but the insert will be blocked.
begin transaction;select employee_id from employees
On Wed, Oct 12, 2005 at 09:30:50PM +0800, Lincoln Yeoh wrote:
> will "lock sometable nowait" help?
>
> http://developer.postgresql.org/docs/postgres/sql-lock.html
>
> If it fails, something is in progress.
And if it succeeds then it might hurt the performance of concurrent
transactions, dependin
will "lock sometable nowait" help?
http://developer.postgresql.org/docs/postgres/sql-lock.html
If it fails, something is in progress.
I believe there are also statement timeouts.
Regards,
Link.
At 11:56 AM 10/12/2005 +, Carlos Benkendorf wrote:
We have applications that are sometimes loc
We have applications that are sometimes locked by a long time application and I would like to avoid these by coding something to discover if the rows are locked before working with them.
Both applications use only inserts in a table with a primary key.
I´m sure that it is not the rigth approach
On Wed, Oct 12, 2005 at 04:11:00AM +, Carlos Benkendorf wrote:
> How can I know which rows are locked?
There's no query that says "show me all rows that are locked"; even
if there was, it would be out of date by the time you got the
results. PostgreSQL 8.1 will enhance pg_locks to show tuple
Hello,
How can I know which rows are locked?
Thanks in advance!
Benkendorf
Promoção Yahoo! Acesso Grátis: a cada hora navegada você acumula cupons e concorre a mais de 500 prêmios! Participe!
On Mon, 14 Dec 1998, The Hermit Hacker wrote:
// row level loocking shoudl be in place for v6.5...not sure about
// on-line recovery, but I *believe* Jan is working on redo-log
// support...
Ooh, is this the kind of log you can use for transaction
replication?
--
Principle Member T
On Mon, 14 Dec 1998, Clark Evans wrote:
> Anyone working on Row level locking and
> on-line recovery?
row level loocking shoudl be in place for v6.5...not sure about
on-line recovery, but I *believe* Jan is working on redo-log support...
Marc G. Fournier
Anyone working on Row level locking and
on-line recovery?
I have some ideas (and questions) in this area.
Also, I was wondering if there is a "transaction
server" project, i.e., a server that helps provide
a consistent client interface to both the database and
application servers.
Thank you!
10 matches
Mail list logo
