Re: BUG #4950: Problem in Job scheduling in Advanced postgre sql

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Ramakanth <ramakanth(at)iblesoft(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4950: Problem in Job scheduling in Advanced postgre sql
Date: 2009-07-29 11:54:21
Message-ID: 603c8f070907290454x1e53cd81ua8c7005c04f2eaaa@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 28, 2009 at 9:26 AM, Ramakanth<ramakanth(at)iblesoft(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      4950
> Logged by:          Ramakanth
> Email address:      ramakanth(at)iblesoft(dot)com
> PostgreSQL version: Advanced 8.3 R2
> Operating system:   Windows xp
> Description:        Problem in Job scheduling in Advanced postgre sql
> Details:
>
> We could not run the scheduled jobs in advanced postgresql.
> But if we go through run now option for a job, it displays the message as
> successful job.
>
> And we had the syntax problem in writing a function to retrieve a table of
> records using if else conditions and plpgsql as the language.
>
> Please look into these issues and get back to us asap.

It sounds to me like the product you are asking about is not
PostgreSQL but some commercial derivative of PostgreSQL, maybe the one
produced by EnterpriseDB. So you probably want to contact them.

...Robert

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Stark 2009-07-29 12:28:21 Re: BUG #4949: NOT IN is prohibitive slower than the rewrite for medium to large sets
Previous Message Axel Fix 2009-07-29 11:01:51 BUG #4954: very slow query with 2 statements