I've tried to run vacuum full analyze with postgresql 8.1.1 and 8.1.2
and in both cases I've seen a segmentation fault.
I read the archives and found something related to 8.1.1 but it was
supposed to be fixed in version 8.1.2.
Is there any patch available ?
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
#0 ArrayGetNItems (ndim=3342336, dims=0x901adf4) at arrayutils.c:62
#1 0x08192b4f in array_cmp (fcinfo=0xfeef8430) at arrayfuncs.c:2678
#2 0x081ff3dd in inlineApplySortFunction (sortFunction=0xfeef9330,
kind=SORTFUNC_CMP, datum1=151127420, isNull1=0 '\0', datum2=151104996,
isNull2=-125 '\203') at tuplesort.c:1899
#3 0x080e2bf9 in compare_scalars (a=0x7083, b=0x0) at analyze.c:2212
#4 0x00231fd0 in msort_with_tmp () from /lib/tls/libc.so.6
#5 0x00231f57 in msort_with_tmp () from /lib/tls/libc.so.6
#6 0x00231f30 in msort_with_tmp () from /lib/tls/libc.so.6
#7 0x00231f30 in msort_with_tmp () from /lib/tls/libc.so.6
#8 0x00231f57 in msort_with_tmp () from /lib/tls/libc.so.6
#9 0x00231f57 in msort_with_tmp () from /lib/tls/libc.so.6
#10 0x002321f8 in qsort () from /lib/tls/libc.so.6
#11 0x080e240d in compute_scalar_stats (stats=0x9017030,
fetchfunc=0x80e1a7c <std_fetch_func>, samplerows=61, totalrows=61)
at analyze.c:1845
#12 0x080e091a in analyze_rel (relid=2620, vacstmt=0x8fe2d88) at
analyze.c:379
#13 0x0810dd12 in vacuum (vacstmt=0x8fe2d88, relids=0xa3c) at vacuum.c:476
#14 0x081895ba in PortalRunUtility (portal=0x8ff4bf0, query=0x8fe2e20,
dest=0x8fe2dd8, completionTag=0xfeef96d0 "") at pquery.c:987
#15 0x0818983a in PortalRunMulti (portal=0x8ff4bf0, dest=0x8fe2dd8,
altdest=0x8fe2dd8, completionTag=0xfeef96d0 "") at pquery.c:1054
#16 0x08189080 in PortalRun (portal=0x8ff4bf0, count=2147483647,
dest=0x8fe2dd8, altdest=0x8fe2dd8, completionTag=0xfeef96d0 "")
at pquery.c:665
#17 0x08185525 in exec_simple_query (query_string=0x8fe2ac8 "VACUUM FULL
ANALYZE VERBOSE;") at postgres.c:1002
#18 0x08187cad in PostgresMain (argc=4, argv=0x8fa2a40,
username=0x8fa2a18 "alfranio") at postgres.c:3217
#19 0x08166979 in BackendRun (port=0x8fba910) at postmaster.c:2859
#20 0x08166489 in BackendStartup (port=0x8fba910) at postmaster.c:2503
#21 0x08164a5f in ServerLoop () at postmaster.c:1236
#22 0x08163f59 in PostmasterMain (argc=6, argv=0x8fa0908) at
postmaster.c:947
#23 0x0812facc in main (argc=6, argv=0x8fa0908) at main.c:263

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
BINDIR = /usr/local/pgsql/bin
DOCDIR = /usr/local/pgsql/doc
INCLUDEDIR = /usr/local/pgsql/include
PKGINCLUDEDIR = /usr/local/pgsql/include
INCLUDEDIR-SERVER = /usr/local/pgsql/include/server
LIBDIR = /usr/local/pgsql/lib
PKGLIBDIR = /usr/local/pgsql/lib
LOCALEDIR =
MANDIR = /usr/local/pgsql/man
SHAREDIR = /usr/local/pgsql/share
SYSCONFDIR = /usr/local/pgsql/etc
PGXS = /usr/local/pgsql/lib/pgxs/src/makefiles/pgxs.mk
CONFIGURE = '--enable-debug' '--enable-dep'
CC = gcc
CPPFLAGS = -D_GNU_SOURCE
CFLAGS = -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -g
CFLAGS_SL = -fpic
LDFLAGS = -Wl,-rpath,/usr/local/pgsql/lib
LDFLAGS_SL =
LIBS = -lpgport -lz -lreadline -ltermcap -lcrypt -lresolv -lnsl -ldl -lm
-lbsd
VERSION = PostgreSQL 8.1.2

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
gcc (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Linux version 2.6.5-1.358 (bhcompile (AT) bugs (DOT) build.redhat.com) (gcc version
3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Sat May 8 09:04:50 EDT 2004




---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Alfranio Correia Junior <alfranio (AT) lsd (DOT) di.uminho.pt> writes:
This looks like a corrupt-data problem to me. If so, this isn't the
way to diagnose it --- you should go about identifying and getting rid
of the corrupted row.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org