| From: | "Jackson, DeJuan" <djackson(at)cpsgroup(dot)com> |
|---|---|
| To: | dimitri(at)France(dot)Sun(dot)COM, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers Mailing List <pgsql-hackers(at)hub(dot)org> |
| Subject: | RE: [GENERAL] SET LOCK MODE ? |
| Date: | 1998-09-03 18:10:38 |
| Message-ID: | F10BB1FAF801D111829B0060971D839F3E2D0F@cpsmail |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
> On Thu, 03 Sep 1998, you wrote:
> >> Is there something like:
> >> SET LOCK MODE {TO WAIT | TO NO WAIT | TO WAIT n}
> >> in postgresql?
> >> Thanks
> >What does it do?
> > -DEJ
>
> It means if during your transaction you've found something
> locked you will WAIT for it, or NO WAIT, or WAIT n seconds.
> It's a standard SQL command, the main idea is to avoid
> the deadlocks.
>
> (dim)
Which standard is it in? I don't believe our current deadlock
resolution supports the syntax, but it may be possible to include it in
v6.5, so I'm sending a copy of this to the HACKERS list.
-DEJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Ryan | 1998-09-03 18:28:33 | Questions about year 2000 compliance and support |
| Previous Message | Jackson, DeJuan | 1998-09-03 18:05:44 | RE: [GENERAL] Optimization problem? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith Parks | 1998-09-03 23:27:34 | Patch for initdb |
| Previous Message | Jackson, DeJuan | 1998-09-03 17:00:47 | RE: [GENERAL] big numbers |