From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Lamar Owen <lowen(at)pari(dot)edu>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: -fpic vs. -fPIC |
Date: | 2003-11-29 18:26:48 |
Message-ID: | 200311291826.hATIQmW11894@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Tom Lane wrote:
> >> The best I have been able to tell is that none of our .so's are anywhere
> >> near large enough to require -fPIC.
>
> > One question would be what happens when it fails? Does it fail visibly
> > so we would hear about it? If so, we can take the risk.
>
> Yes, you'd get a link failure. On the platforms I've seen it on (HPUX
> at least, on an old project with .so's in the dozens-of-megabytes range)
> the error message is pretty specific that you should have used -fPIC.
Great.
In general, I am not sure we are always explicit that taking risks is
contingent on how the user will see a possible failure. For example, if
-fpic generated SELECT query failures randomly, that would be a much
less attractive risk than a link failure.
Risk is a function of both the probability, and the _visibility_ of the
failure.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-11-29 18:37:32 | Automatically force zero_damaged_pages while InRecovery? |
Previous Message | Tom Lane | 2003-11-29 18:21:26 | Re: -fpic vs. -fPIC |