| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kohei Kaigai <Kohei(dot)Kaigai(at)EMEA(dot)NEC(dot)COM> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, Yeb Havinga <yebhavinga(at)gmail(dot)com>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [v9.1] sepgsql - userspace access vector cache |
| Date: | 2011-08-19 15:33:34 |
| Message-ID: | 8367.1313768014@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kohei Kaigai <Kohei(dot)Kaigai(at)EMEA(dot)NEC(dot)COM> writes:
> One point I'm worrying about is a case when contrib/sepgsql is compiled
> with older libselinux than minimum requirement. In this case, we may not
> notice the broken module unless user tries to load it actually.
> Is there a good idea to ensure compile failure when we try to build sepgsql
> module when libselinux-2.0.98 or older was installed?
Well, they should get at least a warning from referencing undefined
functions, no?
There's a limit to how friendly we can be here, since Linux's shlib
stuff is designed to not require all symbols to be resolvable at shlib
construction time. This is one place where Darwin works better ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei Kaigai | 2011-08-19 15:40:13 | Re: [v9.1] sepgsql - userspace access vector cache |
| Previous Message | Robert Haas | 2011-08-19 15:32:49 | Re: [v9.1] sepgsql - userspace access vector cache |