Jeff Davis <pgsql@j-davis.com> writes:
> If a user has custom table access methods, those are likely to be
> required during single user mode anyway (to VACUUM, for instance), so
> we need to be able to load modules during single user mode. I can't
> think of a reason specifically why we can't process
> shared_preload_libraries. Thoughts?
Hmm. There may have been some idea that a library might fail in
single-user mode, and/or have been the cause of you needing to
use single-user in the first place. But if so, you can always
edit it out of shared_preload_libraries. I agree that not
having the option to load it isn't great.
I think that the patch might be missing some stuff. In postmaster.c,
there are several steps after process_shared_preload_libraries()
that look to be there to support loadable libraries, such as
process_shmem_requests(). Wouldn't it be reasonable to expect
that a loadable library would malfunction without those?
(I wonder if we shouldn't refactor this so that the postmaster
and standalone mode share more of the initialization logic.
Keeping these bits in sync seems unlikely to happen otherwise.)
regards, tom lane
