| From: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: old 7.2 bug? |
| Date: | 2002-07-06 21:20:03 |
| Message-ID: | 20020706222003.B23817@quartz.newn.cam.ac.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jul 06, 2002 at 03:53:15PM -0400, Tom Lane wrote:
> Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> > I have had an odd core dump in a bit of code that runs every hour since March
> > 2001, and for some reason just dumped core...
>
> Is the crash reproducible if you run it again?
No, and there wasn't anything special about the line it died on. The
comment
/* Otherwise, start a new block. */
block = (PGresult_data *) malloc(PGRESULT_DATA_BLOCKSIZE);
seems to suggest its a memory thing? It just happened to be one row too
many? But then, the file wasn't *that* big - compared to others that went
through OK..
Cheers,
Patrick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-07-06 21:27:00 | Re: old 7.2 bug? |
| Previous Message | Tom Lane | 2002-07-06 19:53:15 | Re: old 7.2 bug? |