Re: Custom PGC_POSTMASTER GUC variables ... feasible?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Finnerty <jfinnert(at)amazon(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Custom PGC_POSTMASTER GUC variables ... feasible?
Date: 2018-04-10 14:53:06
Message-ID: 20618.1523371986@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Finnerty <jfinnert(at)amazon(dot)com> writes:
> What were the possible failure scenarios that throwing a fatal error was
> intended to avoid, i.e. what sort of "hooking into" is the comment below
> referring to that was regarded as a fate worse than death?

The point is that if the extension is marking the variable as
PGC_POSTMASTER, it's presumably relying on that variable having the same
value in every process. It might be using it as the size of an array in
shared memory, say. If some processes have a different value, that could
end in a memory stomp, or some other crash that's substantially less clean
than a FATAL exit.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2018-04-10 15:03:44 Re: Partitioned tables and covering indexes
Previous Message Nikhil Sontakke 2018-04-10 14:48:27 Re: [HACKERS] logical decoding of two-phase transactions