BUG #11882: make HAVE_WORKING_LINK an option

From: gauchard(at)laas(dot)fr
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #11882: make HAVE_WORKING_LINK an option
Date: 2014-11-05 14:44:48
Message-ID: 20141105144448.26931.18746@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 11882
Logged by: david gauchard
Email address: gauchard(at)laas(dot)fr
PostgreSQL version: 9.4beta2
Operating system: linux
Description:

Hi,

This define "HAVE_WORKING_LINK" should not be always enabled. On systems
that support (and surely use) hard links FS, postgresql might be used on a
subFS not supporting it.
In the sources, the comment is (from git's
src/backend/access/transam/xlog.c):

3373 * Prefer link() to rename() here just to be really sure that we
don't
3374 * overwrite an existing logfile. However, there shouldn't be one,
so
3375 * rename() is an acceptable substitute except for the truly
paranoid.

My thinking is that you may add a '--paranoid' option to use hardlink
instead of rename, or, at least, an option (--relax ?) to disable this
behaviour and use a regular rename() instead.

Just a thought.

david

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message James Pittman 2014-11-05 15:13:29 BUG REPORT: GiST - default operator type for boolean
Previous Message James Pittman 2014-11-05 14:29:40 BUG REPORT: Unable to cast boolean::smallint