On Mon, 23 Oct 2000, Tom Lane wrote: > begin; > select * from foo; -- gets AccessShareLock > LOCK TABLE foo; -- gets AccessExclusiveLock > ... > end; > > this will work currently because the SELECT releases AccessShareLock > when done, but it will deadlock if SELECT does not release that lock. Probably a silly question, but since this is the same transaction, couldn't the lock be 'upgraded' without a problem? Or postgres doesn't currently have idea of lock upgrades...? -alex
- [HACKERS] relation ### modified while in use Alex Pilosov
- Re: [HACKERS] relation ### modified while in use Tom Lane
- Re: [HACKERS] relation ### modified while in ... Alex Pilosov
- Re: [HACKERS] relation ### modified while... Tom Lane
- Re: [HACKERS] relation ### modified w... Alex Pilosov
- Re: [HACKERS] relation ### modif... Tom Lane
- Re: [HACKERS] relation ### modif... Alex Pilosov
- Re: [HACKERS] relation ### modified w... Alex Pilosov
- Re: [HACKERS] relation ### modif... Tom Lane
- Re: [HACKERS] relation ### modified w... Philip Warner
- Re: [HACKERS] relation ### modif... Tom Lane
- Re: [HACKERS] relation ### m... Philip Warner
- Re: [HACKERS] relation ### m... Hiroshi Inoue
- Re: [HACKERS] relation #... Philip Warner
- Re: [HACKERS] relation #... Tom Lane
- Re: [HACKERS] relation #... Philip Warner
- Re: [HACKERS] relation #... Tom Lane
- [HACKERS] Mailing list a... Krzysztof Kowalczyk