On Wed, Nov 16, 2005 at 01:27:29PM +0800, Christopher Kings-Lynne wrote: > >We should probably throw a notice or warning if we go to a table lock, > >too. > > That's not very useful, because you can only do somethign about it AFTER > the 1 hour exclusive lock merge has already run :)
Not true; it would be useful for development when you'd like to know that some statement is grabbing a table lock. This is something that you wouldn't normally notice in a dev environment, and it sounds like it'd be easy to do a merge that has the unintended effect of grabbing a table lock. -- Jim C. Nasby, Sr. Engineering Consultant [EMAIL PROTECTED] Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461 ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
