Re: Custom PGC_POSTMASTER GUC variables ... feasible?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Alex Hunsaker" <badalex(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Custom PGC_POSTMASTER GUC variables ... feasible?
Date: 2009-01-03 20:00:52
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

"Alex Hunsaker" <badalex(at)gmail(dot)com> writes:
> Right I agree this is a non-issue. For that matter if I really wanted
> to muck with it I could just set
> process_shared_preload_libraries_in_progress = true in my _PG_init
> function. And I guess if anyone thinks thats a problem we can mark
> the flag as static and only export a function for reading the value.

Yeah, I thought about that and decided to leave it as a variable ---
if anyone actually has a good reason to do it, they have an (ugly)
workaround available this way. We're only trying to catch errors
of omission, not prevent C-level code from subverting the system
if it wants to.

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-01-03 20:14:25 Re: contrib/pg_stat_statements 1226
Previous Message Alex Hunsaker 2009-01-03 20:00:35 Re: contrib/pg_stat_statements 1226