Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> I don't. It's from the interlock that prevents copying a database that > >> contains active sessions. > > > I understand that, but why does psql still hold that lock while > > displaying the database names with more? > > I don't think it closes the database connection until it's ready to > exit. > > We could maybe fix -l to close the connection before outputting data, > but it doesn't seem like that really will make a lot of difference. > What of someone who's connected to template1 with a plain "psql > template1" session?
Oh, so it is their connection to template1 that is causing the lock, not the display of the -l data. Thanks, got it, and makes sense. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
