![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Adrian Calvin wrote: When "psql -l" is invoked from prompt, and a user lets it sit at the 'more' prompt, no other user can create a database. The "cannot access template..." error is thrown. Has this been corrected in later versions? Sorry, I have trouble believing that. |
#2
| |||
| |||
|
|
Bruce Momjian <pgman (AT) candle (DOT) pha.pa.us> writes: Adrian Calvin wrote: When "psql -l" is invoked from prompt, and a user lets it sit at the 'more' prompt, no other user can create a database. The "cannot access template..." error is thrown. Has this been corrected in later versions? Sorry, I have trouble believing that. I don't. It's from the interlock that prevents copying a database that contains active sessions. |
#3
| |||
| |||
|
|
Bruce Momjian <pgman (AT) candle (DOT) 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? |
![]() |
| Thread Tools | |
| Display Modes | |
| |