Re: BUG #11882: make HAVE_WORKING_LINK an option - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #11882: make HAVE_WORKING_LINK an option
Date
Msg-id 6399.1415320297@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #11882: make HAVE_WORKING_LINK an option  (David Gauchard <gauchard@laas.fr>)
List pgsql-bugs
David Gauchard <gauchard@laas.fr> writes:
> On mer., nov. 05, 2014 at 05:35:14 +0100, Andres Freund wrote:
>> On 2014-11-05 14:44:48 +0000, gauchard@laas.fr wrote:
>>> 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.

>> Those FS's really shouldn't be used for a database though. Are you
>> thinking of something concrete?

> I was working on a fuse filesystem which I test using the
> phoronix test suite, which uses postgresql for benchmarking, when
> I ran into this bug (hard link is not always implementable).

Meh.  There's a reason HAVE_WORKING_LINK is defined in pg_config_manual.h:
if you want to adjust it, you're supposed to do so manually.

I don't really want to carry a configure option to support
non-production-quality filesystems.  Even just documenting it
would be painful (are we really going to have an option that
we'd tell people not to use?)

            regards, tom lane

pgsql-bugs by date:

Previous
From: David Gauchard
Date:
Subject: Re: BUG #11882: make HAVE_WORKING_LINK an option
Next
From: Tom Lane
Date:
Subject: Re: BUG #11901: Full text search: thesaurus size limit