Le jeudi 19 novembre 2009 à 07:01:57, Shruthi A a écrit :
> Wow! Thanks a lot! That was a great deal of help! :-)
>
> On Wed, Nov 18, 2009 at 8:41 PM, Jure Kobal <j.kobal@gmx.com> wrote:
> > > -- While running the pgagent daemon, what dbname should i specify? Is
> > > it postgres or pgadmin (as the example in
> >
> > http://www.enterprisedb.com/docs/en/8.3/tools/pgadmin/1.8.2/pgagent-insta
> >ll
> >
> > > .html) ?
> >
> > postgres. Since that is the database, pgagent is only a schema inside it.
>
> The problem is that sites like the above and
>
> http://www.pgadmin.org/docs/1.8/pgagent-install.html
> are misleading, giving dbname=pgadmin in their example, while they clearly
> mention that we should create the pgagent catalogs in the 'postgres'
> database. Really careless of them!
>
This is fixed right now.
BTW, rather than complaining only, you should send us an email so that we can
fix those issues ASAP.
> [...]
> initially thought by looking at pgagent --help which claims that with the
> -l option, 0 is error, 1 is warning, 2 is debug and 0 is default. So i
> had thought that any error should be automatically flagged by the process
> when i run it in foreground (-f). Including 'database pgadmin does not
> exist'. But it didn't. On further investigation after your suggestion, i
> found that this is considered only a 'warning' and not an 'error'! So it
> is flagged with -l 1 or 2, but not with 0. Isn't this ridiculous!
>
Dave's answer to this:
It's a warning because it doesn't cause a hard failure. It'll keep
trying to connect, and then give up with an error after 10 or so
attempts over a period of time. It's done that way to allow for race
conditions in init scripts, or systems where PostgreSQL starts in a
timely fashion, but doesn't come up immediately because it goes into
recovery for example.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
