Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Any suggestions how to extract some info out of this?

> Does OS X have the catchsegv tool?

No, but I suddenly remembered about CrashReporter, and sure enough it's
catching these crashes:

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000010

Thread 0 Crashed:
0   postmaster  0x001af4ef smgrextend + 12 (smgr.c:485)
1   postmaster  0x00029044 end_heap_rewrite + 208 (rewriteheap.c:278)
2   postmaster  0x000bdc22 cluster_rel + 850 (cluster.c:806)
3   postmaster  0x000be119 cluster + 160 (cluster.c:220)
4   postmaster  0x001b74a8 PortalRunUtility + 233 (palloc.h:84)
5   postmaster  0x001b7784 PortalRunMulti + 237 (pquery.c:1271)
6   postmaster  0x001b80ae PortalRun + 918 (pquery.c:813)
7   postmaster  0x001b2afd exec_simple_query + 656 (postgres.c:965)
8   postmaster  0x001b4b0c PostgresMain + 5628 (postgres.c:3507)
9   postmaster  0x00183973 ServerLoop + 2828 (postmaster.c:2614)
10  postmaster  0x00184b1e PostmasterMain + 2794 (postmaster.c:972)
11  postmaster  0x00130f8e main + 1236 (main.c:188)
12  postmaster  0x00001e86 _start + 216
13  postmaster  0x00001dad start + 41

So it looks like this has got something to do with the MVCC-safe cluster
changes, which is not too surprising considering it started happening
around about then.  Off to have a look ...

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
       subscribe-nomail command to [EMAIL PROTECTED] so that your
       message can get through to the mailing list cleanly

Reply via email to