[BUGS] BUG #5304: psql using conninfo fails in connecting to the server
The following bug has been logged online: Bug reference: 5304 Logged by: Fujii Masao Email address: masao.fu...@gmail.com PostgreSQL version: HEAD Operating system: RHEL5.1 Description:psql using conninfo fails in connecting to the server Details: In HEAD, psql using conninfo fails in connecting to the server as follows. $ bin/psql "host=localhost" psql: FATAL: database "host=localhost" does not exist This is because the recently-introduced PQconnectStartParams() doesn't handle correctly the dbname parameter containing '='. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5304: psql using conninfo fails in connecting to the server
Fujii Masao wrote: > In HEAD, psql using conninfo fails in connecting to the server as follows. > > $ bin/psql "host=localhost" > psql: FATAL: database "host=localhost" does not exist > > This is because the recently-introduced PQconnectStartParams() > doesn't handle correctly the dbname parameter containing '='. Hmm, I don't think that was ever really supposed to work, it was accidental that it did. I certainly didn't realize you could do that. The documented way to do that is: bin/psql --host=localhost -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5304: psql using conninfo fails in connecting to the server
On Mon, Feb 1, 2010 at 5:31 PM, Heikki Linnakangas wrote: > Fujii Masao wrote: >> In HEAD, psql using conninfo fails in connecting to the server as follows. >> >> $ bin/psql "host=localhost" >> psql: FATAL: database "host=localhost" does not exist >> >> This is because the recently-introduced PQconnectStartParams() >> doesn't handle correctly the dbname parameter containing '='. > > Hmm, I don't think that was ever really supposed to work, it was > accidental that it did. I certainly didn't realize you could do that. > The documented way to do that is: > > bin/psql --host=localhost Really? According to the document, psql using conninfo seems to be supported. http://developer.postgresql.org/pgdocs/postgres/app-psql.html#R2-APP-PSQL-CONNECTING > An alternative way to specify connection parameters is in a conninfo > string, which is used instead of a database name. This mechanism give > you very wide control over the connection. For example: > > $ psql "service=myservice sslmode=require" Am I missing something? Regards, -- Fujii Masao NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5304: psql using conninfo fails in connecting to the server
2010/2/1 Fujii Masao : > On Mon, Feb 1, 2010 at 5:31 PM, Heikki Linnakangas > wrote: >> Fujii Masao wrote: >>> In HEAD, psql using conninfo fails in connecting to the server as follows. >>> >>> $ bin/psql "host=localhost" >>> psql: FATAL: database "host=localhost" does not exist >>> >>> This is because the recently-introduced PQconnectStartParams() >>> doesn't handle correctly the dbname parameter containing '='. >> >> Hmm, I don't think that was ever really supposed to work, it was >> accidental that it did. I certainly didn't realize you could do that. >> The documented way to do that is: >> >> bin/psql --host=localhost > > Really? According to the document, psql using conninfo seems to > be supported. > > http://developer.postgresql.org/pgdocs/postgres/app-psql.html#R2-APP-PSQL-CONNECTING Yes, that is definitely supposed to work. It was intentionally added in 8.3 and is very useful :-) -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5304: psql using conninfo fails in connecting to the server
Heikki Linnakangas writes: > Fujii Masao wrote: >> In HEAD, psql using conninfo fails in connecting to the server as follows. >> >> $ bin/psql "host=localhost" >> psql: FATAL: database "host=localhost" does not exist >> >> This is because the recently-introduced PQconnectStartParams() >> doesn't handle correctly the dbname parameter containing '='. > Hmm, I don't think that was ever really supposed to work, it was > accidental that it did. No, it was intentional. regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #5304: psql using conninfo fails in connecting to the server
On 02/01/2010 08:06 AM, Tom Lane wrote: > Heikki Linnakangas writes: >> Fujii Masao wrote: >>> In HEAD, psql using conninfo fails in connecting to the server as follows. >>> >>> $ bin/psql "host=localhost" >>> psql: FATAL: database "host=localhost" does not exist >>> >>> This is because the recently-introduced PQconnectStartParams() >>> doesn't handle correctly the dbname parameter containing '='. > >> Hmm, I don't think that was ever really supposed to work, it was >> accidental that it did. > > No, it was intentional. Will fix. Give me a day or so though. Joe signature.asc Description: OpenPGP digital signature
[BUGS] BUG #5305: Postgres service stops when closing Windows session
The following bug has been logged online: Bug reference: 5305 Logged by: Cristian Email address: cbit...@gmail.com PostgreSQL version: 8.3.9 Operating system: Windows 2003 Server Standard x64 Description:Postgres service stops when closing Windows session Details: We connect to Windows server using the Terminal Services Clients (mstsc), and performs maintenance task with pgAdmin 3. PostgreSQL service crashes when the user close session on Windows, and the following error is recorded in the pg_log files: LOG: server process (PID 5200) exited with exit code 128 LOG: terminating any other active server processes WARNING: terminating connection because of crash of another server process DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. HINT: In a moment you should be able to reconnect to the database and repeat your command. .. The server has the following specs: Windows 2003 SP2 Standard 64-bit, 4GB, NOT joined to a domain. PostgreSQL 8.3.9 pgAdmin 3 We connect without the /console parameter. Any ideas? -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
