postgres

History

Tom Lane bd02b48ba4 Make FOR UPDATE/SHARE in the primary query not propagate into WITH queries; for example in WITH w AS (SELECT * FROM foo) SELECT * FROM w, bar ... FOR UPDATE the FOR UPDATE will now affect bar but not foo. This is more useful and consistent than the original 8.4 behavior, which tried to propagate FOR UPDATE into the WITH query but always failed due to assorted implementation restrictions. Even though we are in process of removing those restrictions, it seems correct on philosophical grounds to not let the outer query's FOR UPDATE affect the WITH query. In passing, fix isLockedRel which frequently got things wrong in nested-subquery cases: "FOR UPDATE OF foo" applies to an alias foo in the current query level, not subqueries. This has been broken for a long time, but it doesn't seem worth back-patching further than 8.4 because the actual consequences are minimal. At worst the parser would sometimes get RowShareLock on a relation when it should be AccessShareLock or vice versa. That would only make a difference if someone were using ExclusiveLock concurrently, which no standard operation does, and anyway FOR UPDATE doesn't result in visible changes so it's not clear that the someone would notice any problem. Between that and the fact that FOR UPDATE barely works with subqueries at all in existing releases, I'm not excited about worrying about it.		16 years ago
..
Makefile	Revert updatable views	17 years ago
rewriteDefine.c	8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list	17 years ago
rewriteHandler.c	Make FOR UPDATE/SHARE in the primary query not propagate into WITH queries;	16 years ago
rewriteManip.c	Fix subquery pullup to wrap a PlaceHolderVar around the entire RowExpr	17 years ago
rewriteRemove.c	8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list	17 years ago
rewriteSupport.c	Update copyright for 2009.	17 years ago