| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Sabin Coanda <sabin(dot)coanda(at)deuromedia(dot)ro> |
| Cc: | pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: pgAgent service problem |
| Date: | 2007-03-16 23:17:32 |
| Message-ID: | 45FB258C.4010100@postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
Sabin Coanda wrote:
> ...
>> No idea, noone ever reported such a crash before. Can you supply a level
>> 2 (debug) log from when the crash occurs? A pg_dump of your pgagent
>> schema would help as well.
>>
>> Regards, Dave
>
> Hi Dave,
>
> I just captured the significant event log sequence and I attached it.
> However, I found that sometimes it runs well at the same job step.
>
> The step command is the following:
> "C:\Program Files\PostgreSQL\8.2\bin\pg_dump.exe" -F p -v -U
> postgres -d -D -f "C:\Program
> Files\PostgreSQL\8.2\data\bak\dipDB_%DATE:~0,2%%DATE:~3,2%%DATE:~6,2%%TIME:~0,2%%TIME:~3,2%%TIME:~6,2%.sql"
> "dbTest_local"
I think I've fixed the bug - can I email you a .exe to try?
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Shellam | 2007-03-18 12:26:28 | Default "maximum rows to retrieve" setting |
| Previous Message | Sabin Coanda | 2007-03-16 13:42:02 | Re: pgAgent service problem |