Re: libpq connection timeout mismanagement
| От | Fabien COELHO |
|---|---|
| Тема | Re: libpq connection timeout mismanagement |
| Дата | |
| Msg-id | alpine.DEB.2.21.1808140909250.27691@lancre обсуждение исходный текст |
| Ответ на | Re: libpq connection timeout mismanagement (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: libpq connection timeout mismanagement
|
| Список | pgsql-hackers |
Hello Tom, >> connect_timeout=2.9 is accepted and considered as meaning 2. >> connect_timeout=-10 or connect_timeout=two are also accepted and mean >> forever. Probably thanks to "atoi". > > Right. As before, I'm not excited about rejecting trailing junk, > considering we never did before. My 0.02€: accepting trailing junk is just a recipee for hiding bugs: sh> psql "connect_timeout=2,port=5433" psql> \conninfo ... port=5432 # port directive was silently ignored So erroring out would be a good thing, and it could be done on a new release. At the minimum there should be a warning. -- Fabien.
В списке pgsql-hackers по дате отправления: