Re: Potential issue with pgAgent when updating pga_jobsteplog
От | Dave Page |
---|---|
Тема | Re: Potential issue with pgAgent when updating pga_jobsteplog |
Дата | |
Msg-id | 937d27e10805060357l11e67d2dg6a55f8a5f29ca3f0@mail.gmail.com обсуждение исходный текст |
Ответ на | Potential issue with pgAgent when updating pga_jobsteplog ("Benjamin Krajmalnik" <kraj@illumen.com>) |
Ответы |
Re: Potential issue with pgAgent when updating pga_jobsteplog
|
Список | pgadmin-support |
On Mon, May 5, 2008 at 4:57 PM, Benjamin Krajmalnik <kraj@illumen.com> wrote: > > I believe one of 2 things probably needs to be done: > > 1. Update the documentation to mention what range the result needs to be. > This means that queries which affect many rows need to be encapsulated in a > stored procedure or have a supplementary query such as "select 1" added to > the step in order to return an in-range value > 2. Change jslresult to a data type which will accomodate a larger value. I've gone with the second option and increased the jslresult column to be an int4 (matching the C++ code). You should be able to increase the column size on your server as no other code changes are required. Thanks, Dave -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
В списке pgadmin-support по дате отправления: