Re: BUG #15350: Getting invalid cache ID: 11 Errors
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>,
Kieran McCusker <kieran.mccusker@gmail.com>,
PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2018-09-13T01:51:19Z
Lists: pgsql-bugs
Thomas Munro <thomas.munro@enterprisedb.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
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Defer restoration of libraries in parallel workers.
- de4fe83c7e6d 9.6.11 landed
- 98a4e814e473 10.6 landed
- 9d178fb92804 11.0 landed
- 6c3c9d418918 12.0 landed