Steve Crawford wrote:
> Sysadmin wrote:
>> Hi all,
>>
>> I'm finding that routinely when I try to reload a database on a server
>> where I know there are no connections to a given DB I get the error:
>>
>> $ dropdb foo && createdb foo -O bar && psql foo -f /path/to/db.out
>> dropdb: database remo
Two vaguely helpful comments:
1. Sometimes this has happened to me when I unknowingly have two
terminal psql processes running on the same machine that I'm using to
connect to the server. Everyone but yourself may be off the database,
but there may be two instances of yourself. :)
2. I've
Tom Lane wrote:
> Sysadmin <[EMAIL PROTECTED]> writes:
>> I'm finding that routinely when I try to reload a database on a server
>> where I know there are no connections to a given DB I get the error:
>
>> $ dropdb foo && createdb foo -O bar && psql foo -f /path/to/db.out
>> dropdb: database rem
Sysadmin wrote:
> Hi all,
>
> I'm finding that routinely when I try to reload a database on a server
> where I know there are no connections to a given DB I get the error:
>
> $ dropdb foo && createdb foo -O bar && psql foo -f /path/to/db.out
> dropdb: database removal failed: ERROR: database
Sysadmin <[EMAIL PROTECTED]> writes:
> I'm finding that routinely when I try to reload a database on a server
> where I know there are no connections to a given DB I get the error:
> $ dropdb foo && createdb foo -O bar && psql foo -f /path/to/db.out
> dropdb: database removal failed: ERROR: dat
Hi all,
I'm finding that routinely when I try to reload a database on a server
where I know there are no connections to a given DB I get the error:
$ dropdb foo && createdb foo -O bar && psql foo -f /path/to/db.out
dropdb: database removal failed: ERROR: database "foo" is being
accessed by oth
