Re: When "psql -l" is invoked from prompt and not completed,

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Adrian Calvin <acexec(at)yahoo(dot)com>, pgsql-bugs-owner(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Re: When "psql -l" is invoked from prompt and not completed,
Date: 2003-07-24 22:07:46
Message-ID: 23790.1059084466@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> 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?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2003-07-24 22:12:48 Re: When "psql -l" is invoked from prompt and not completed,
Previous Message Bruce Momjian 2003-07-24 21:54:08 Re: When "psql -l" is invoked from prompt and not completed,