Re: Segmentation fault while COPY in 7.3
Bruce Momjian <pgman@candle.pha.pa.us>
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Medi Montaseri <medi.montaseri@intransa.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Nicolai Tufar <ntufar@apb.com.tr>, pgsql-general@postgresql.org
Date: 2002-12-03T19:51:23Z
Lists: pgsql-hackers, pgsql-general
I was wrong. We found a COPY bug in 7.3 that will be fixed in 7.3.1. Would you compile with symbols, -g, and send a new backtrace? --------------------------------------------------------------------------- Medi Montaseri wrote: > FYI, I'm experiencing this with Async Queries (Async Purge and Aysnc > Vacuum). > > Tom Lane wrote: > > >Bruce Momjian <pgman@candle.pha.pa.us> writes: > > > > > >>Yes, we found a double pfree in 7.3. There will be a fix in 7.3.1. > >> > >> > > > >The double pfree was in COPY, though. This looks to be a different > >issue. > > > > > > > >>>(gdb) > >>>#0 0x00420874 in heap_freetuple () > >>>#1 0x004a8390 in acquire_sample_rows () > >>>#2 0x004a75c8 in analyze_rel () > >>>#3 0x0049f690 in vacuum () > >>>#4 0x005585d8 in ProcessUtility () > >>>#5 0x00553c78 in pg_exec_query_string () > >>>#6 0x00555850 in PostgresMain () > >>> > >>> > > > > regards, tom lane > > > > > > > > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073