Re: When "psql -l" is invoked from prompt and not completed, - Mailing list pgsql-bugs

From Tom Lane
Subject Re: When "psql -l" is invoked from prompt and not completed,
Date
Msg-id 23790.1059084466@sss.pgh.pa.us
Whole thread Raw
In response to Re: When "psql -l" is invoked from prompt and not completed,  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: When "psql -l" is invoked from prompt and not completed,
List pgsql-bugs
Bruce Momjian <pgman@candle.pha.pa.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

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: When "psql -l" is invoked from prompt and not completed,
Next
From: Bruce Momjian
Date:
Subject: Re: When "psql -l" is invoked from prompt and not completed,