| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CustomScan support on readfuncs.c |
| Date: | 2015-11-09 15:24:26 |
| Message-ID: | CA+TgmoZj_uTKfqk-kx9pXV9S+M0R=1+ifKQHCV-nj820oXtoyg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Nov 7, 2015 at 6:38 AM, Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com> wrote:
> Are you suggesting to pass the object name on software build time?
Yes. That's what test_shm_mq and worker_spi already do:
sprintf(worker.bgw_library_name, "test_shm_mq");
> If so, it may load incorrect libraries when DBA renamed its filename.
> At least, PostgreSQL cannot prevent DBA to rename library filenames
> even if they try to deploy "pg_strom.so", "pg_strom.20151106.so" and
> "pg_strom.20151030_bug.so" on same directory.
I agree. But that's not a new problem that needs to be solved by this
patch. It already exists - see above.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-11-09 15:37:17 | Re: Extracting fields from 'infinity'::TIMESTAMP[TZ] |
| Previous Message | Peter Eisentraut | 2015-11-09 15:21:43 | pgsql: Translation updates |