RE: AW: AW: Issue NOTICE for attempt to raise lock leve l? - Mailing list pgsql-hackers

From Mikheev, Vadim
Subject RE: AW: AW: Issue NOTICE for attempt to raise lock leve l?
Date
Msg-id 8F4C99C66D04D4118F580090272A7A234D314F@sectorbase1.sectorbase.com
Whole thread Raw
Responses Re: AW: AW: Issue NOTICE for attempt to raise lock leve l?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > Will we still have readers-dont-block-writers behaviour?
> 
> Sure.  The only thing this really affects is VACUUM and 
> schema-altering
> commands, which will now have to wait until reader 
> transactions commit.
> In other words
> 
>     Session 1            Session 2
> 
>     BEGIN;
>     SELECT * FROM foo;
> 
>                     ALTER TABLE foo ...
> 
>     ...
> 
>     COMMIT;
> 
> Session 2 will have to wait for session 1 to commit; before it didn't.

Not only, Tom -:)
Unfortunately, session 3 with just SELECT * FROM foo will also wait
for session 1 & session 2 commit.

Vadim


pgsql-hackers by date:

Previous
From: "Kevin O'Gorman"
Date:
Subject: Need a debugging tip or two
Next
From: Tom Lane
Date:
Subject: Re: AW: Issue NOTICE for attempt to raise lock level?