Hiroshi Inoue <[EMAIL PROTECTED]> writes:
> I'm not sure about the use of AccessShareLock in parse-analyze-
> optimize phase however.

That's something we'll have to clean up while fixing this.  Currently
the system may acquire and release AccessShareLock multiple times while
parsing/rewriting/planning.  We need to make sure that an appropriate
lock is grabbed at *first* use and then held.

Should save a few cycles as well as being more correct ...

                        regards, tom lane

Reply via email to