Skip site navigation (1) Skip section navigation (2)

Re: Backend working directories and absolute file paths

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Backend working directories and absolute file paths
Date: 2005-06-30 20:48:56
Message-ID: 21494.1120164536@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Greg Stark <gsstark(at)mit(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2005-06-30 21:06:22
Subject: Re: WAL oddities (8.0.3)
Previous:From: Greg StarkDate: 2005-06-30 20:31:56
Subject: Re: Backend working directories and absolute file paths

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group