Greg Stark <gsstark@mit.edu> writes:
> However it might be nice to have dumps go to a configurable place.
You'd have to talk to your kernel provider about that one; we don't have
any direct control over where or even whether core dumps occur.
> There's another approach that seems more robust. When initdb is run randomly
> generate a unique id. Then whenever creating files include that unique id in
> the first block of the file. Whenever you open a file sanity check the first
> block. If it doesn't match PANIC immediately. (hm, actually you don't even
> need to PANIC, jut shutting the one backend should be enough.)
This adds overhead, rather than removing it as I was hoping to do.
regards, tom lane