Re: [pgsql-www] Server unreliability
От | Gavin Sherry |
---|---|
Тема | Re: [pgsql-www] Server unreliability |
Дата | |
Msg-id | Pine.LNX.4.58.0410022333110.30224@linuxworld.com.au обсуждение исходный текст |
Ответ на | Re: [pgsql-www] Server unreliability ("Marc G. Fournier" <scrappy@postgresql.org>) |
Список | pgsql-advocacy |
On Wed, 29 Sep 2004, Marc G. Fournier wrote: > On Wed, 29 Sep 2004, Alvaro Herrera wrote: > > > about pg_query not getting a good connection or similar problems. > > Isn't normal advice to check return codes before even trying to use the > > connections? Why isn't this done in the main postgresql.org code, where > > anyone can see it, is beyond me. Of course the solution to the > > underlying problem is to restart the Postgres server, but why should we > > inform the user that Postgres' own database server is down, in the worst > > possible way? > > Just curious here, but when/where? We haven't had a database issue in > quite awhile that *I'm* aware of ... in fact, the whole web site is > static, generated periodically from .php files, so that the mirrors can > pick things up properly, so there should never be a 'cannot connect to > database' issue, since there are no connections to the database being made I know this isn't on the main site but: http://www.alcove.com.au/~swm/gborg.png Gavin
В списке pgsql-advocacy по дате отправления: