| 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: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: old 7.2 bug? |
| Date: | 2002-07-07 09:12:42 |
| Message-ID: | 20020707101242.B25499@quartz.newn.cam.ac.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jul 06, 2002 at 05:27:00PM -0400, Tom Lane wrote:
> Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk> writes:
> > seems to suggest its a memory thing? It just happened to be one row too
> > many?
>
> But the query was only one row, no? Seems unlikely that it ran out of
> memory (especially if the core dump file is not large).
...
Thank you for the suggestions. It being not reproducible means the problem
will be hard to find (still wonder why yyparse() didn't appear in the
core dump..), or of course play Russian roulette - one core dump in over a
year isn't exactly bad :)
Cheers,
Patrick
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tony | 2002-07-07 09:43:22 | Re: database backup |
| Previous Message | Hans-Juergen Schoenig | 2002-07-07 08:48:51 | PostgreSQL doesn't use indexes even is enable_seqscan = off |