Tom Lane wrote:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
But I did notice that we're not fsyncing the newly written relation like
we should.
Good point, but doesn't the analogy to copy_relation_data say that we
should sync if not rd_istemp?
Right. I don't know why I didn't copy that i
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
> But I did notice that we're not fsyncing the newly written relation like
> we should.
Good point, but doesn't the analogy to copy_relation_data say that we
should sync if not rd_istemp? (This is my fault BTW; your original
patch kept the data in s
I wrote:
> 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)
AFAICS, a crash i
Tom Lane wrote:
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_ACCES
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
Tom Lane wrote:
Any suggestions how to extract some info out of this?
Does OS X have the catchsegv tool? If you can run postmaster with that,
you should get a backtrace when it crashes. Unless it has the same
problem as gdb, of course..
--
Heikki Linnakangas
EnterpriseDB http://www.en
Tom Lane wrote:
> Dunno if anyone's noticed, but buildfarm member jackal has been crashing
> intermittently in the "cluster" regression test. I found out that I can
> reproduce that here on a Mac Mini (apparently the same or nearly same
> hardware/software as jackal) --- just repeat the parallel t
