Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #26870
| References | <CAPTjJmqD6oRXFYdfi-Da13a6sLpy=v84Tc8Bq2-m+rQArqbvMA@mail.gmail.com> <D960CB61B694CF459DCFB4B0128514C208419D00@exadv11.host.magwien.gv.at> |
|---|---|
| Date | 2012-08-11 00:00 +1000 |
| Subject | Re: [GENERAL] Postgres and Upstart |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.3160.1344607204.4697.python-list@python.org> (permalink) |
On Fri, Aug 10, 2012 at 11:56 PM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote: > Chris Angelico wrote: >> I'm looking for a reliable way to be sure that Postgres has finished >> its initialization and is ready to rumble. > > The normal way to test this is a connection attempt. > You could also look into the server logs for the > appropriate message, but that seems more fragile and difficult. Yeah, I can poll it, and that's what I do in a couple of places; but somewhere in the code, it probably "knows" that it's ready. I can keep doing what I'm doing, but was hoping for an event-driven approach. Thanks! ChrisA
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: [GENERAL] Postgres and Upstart Chris Angelico <rosuav@gmail.com> - 2012-08-11 00:00 +1000
csiph-web