Re: psql doesn't reuse -p after backend fail
От | Tom Lane |
---|---|
Тема | Re: psql doesn't reuse -p after backend fail |
Дата | |
Msg-id | 11444.1315247243@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | psql doesn't reuse -p after backend fail (hubert depesz lubaczewski <depesz@depesz.com>) |
Ответы |
Re: psql doesn't reuse -p after backend fail
Re: psql doesn't reuse -p after backend fail |
Список | pgsql-bugs |
hubert depesz lubaczewski <depesz@depesz.com> writes: > ran psql with specyfying port: > psql -p 4329 -U postgres -d some_database > then I run query which breaks backend: > =# select * from categories limit 1; > The connection to the server was lost. Attempting reset: Failed. > !> > When I'll try to re-issue \c some_database now, I got: > !> \c some_database > could not connect to server: No such file or directory > Is the server running locally and accepting > connections on Unix domain socket "/tmp/.s.PGSQL.5432"? > !> It's not just the port, it's all the connection parameters --- do_connect relies on the PGconn object to remember those, and in this case there no longer is a PGconn object. We could have psql keep that information separately, but I'm not sure it's really worth the trouble. regards, tom lane
В списке pgsql-bugs по дате отправления: