Re: BUG #11882: make HAVE_WORKING_LINK an option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Gauchard <gauchard(at)laas(dot)fr>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #11882: make HAVE_WORKING_LINK an option
Date: 2014-11-07 00:31:37
Message-ID: 6399.1415320297@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

David Gauchard <gauchard(at)laas(dot)fr> writes:
> On mer., nov. 05, 2014 at 05:35:14 +0100, Andres Freund wrote:
>> On 2014-11-05 14:44:48 +0000, gauchard(at)laas(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-11-07 00:37:13 Re: BUG #11901: Full text search: thesaurus size limit
Previous Message Burgess, Freddie 2014-11-06 23:37:23 Invalid page in block on autovacuum