Re: BUG #3667: Job scheduling with Greenplum fails
От | Dave Page |
---|---|
Тема | Re: BUG #3667: Job scheduling with Greenplum fails |
Дата | |
Msg-id | 200710152254130000@3036129777 обсуждение исходный текст |
Ответ на | BUG #3667: Job scheduling with Greenplum fails ("Jon Roberts" <jon.roberts@asurion.com>) |
Ответы |
Re: BUG #3667: Job scheduling with Greenplum fails
|
Список | pgsql-bugs |
> ------- Original Message ------- > From: Simon Riggs <simon@2ndquadrant.com> > To: "Roberts, Jon" <Jon.Roberts@asurion.com> > Sent: 15/10/07, 21:19:04 > Subject: Re: [BUGS] BUG #3667: Job scheduling with Greenplum fails > > On Thu, 2007-10-11 at 10:42 -0500, Roberts, Jon wrote: > > > Like I said in the email, I think the best solution is to put the code in a > > function. However, after I inserted a total of 25 jobs, the difference is > > more noticeable and my sql is better in terms of cost and total time. > > You're missing a few key points: > > - this isn't the PgAdmin hackers list, so you're asking in the wrong > place ... go to www.pgadmin.org and go from there. This is the standard > PostgreSQL bug list and you haven't shown any bug with standard > PostgreSQL. > > - PgAdmin 1.8 is almost released so you may have missed the boat > > - pgAdmin is trying to work with other PG variants, so a reasoned > argument, in the right place, may help. A change has been applied for GP compatibility. It will be in pgAdmin 1.8. Regards, Dave
В списке pgsql-bugs по дате отправления: