steps to reproduce: session1: connect using user1 to database1. session2: connect using user2 to database2. session1: create table x ( y int); session2: begin; session1: create index concurrently q on x(y); it hangs. session2: rollback/commit; session1: finishes.
i dont really see why this would be neccessary - i understand that we need to wait for transactions in the same db, but waiting for transaction in another database? i tested it on 8.2.4 and 8.3devel from cvs-head, fetched 3 days ago. depesz -- quicksil1er: "postgres is excellent, but like any DB it requires a highly paid DBA. here's my CV!" :) http://www.depesz.com/ - blog dla ciebie (i moje CV) ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
