| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Kieran McCusker <kieran(dot)mccusker(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #15350: Getting invalid cache ID: 11 Errors |
| Date: | 2018-09-13 01:51:19 |
| Message-ID: | 5225.1536803479@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> ... Do we really want to crack down on
> extension libraries that wouldn't work in shared_preload_libraries?
That is, perhaps, a fair question; but I see little benefit to users
in such a library design. Most people who are using a library heavily
would likely wish to have it preloaded.
> What about hypothetical libraries that are smart enough to avoid
> making such calls when they detect that they're running from
> shared_preload_libraries -- you'd generate false warnings when loaded
> the regular way.
I find that argument too thin to take seriously. If the library
can manage that, it might as well just postpone the calls all the
time, rather than have two different operating modes that would
require separate testing. What would be the advantage of the
extra complication?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kalyani kaniganti | 2018-09-13 02:07:17 | Re: BUG #15376: Postgres sql 9.4.19 pg_upgrade stops with error The source cluster was not shut down cleanly. |
| Previous Message | Thomas Munro | 2018-09-13 01:42:00 | Re: BUG #15350: Getting invalid cache ID: 11 Errors |