You are talking about a shmem block using by the backend, right? Or about my "own" shmem block?. I'm very interested in the implementation of a "constants" like functionality to pgsql, but I don't know where to start with... Any help or ideas? -----Original Message----- From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx] Sent: Domingo, 16 de Octubre de 2005 10:42 p.m. To: Douglas McNaught Cc: cristian@xxxxxxxxxxxxxxx; tjo@xxxxxxx; pgsql-general@xxxxxxxxxxxxxx Subject: Re: dynamic loading of .so Douglas McNaught <doug@xxxxxxxxxxxx> writes: > <cristian@xxxxxxxxxxxxxxx> writes: >> are there any way to make them global for all the instances? > Put them in shared memory. This probably isn't trival, as all the > shared memory is allocated up front and used for existing purposes (at > least, as I understand it). There's a "slop factor" of 100KB or so in the shared memory size calculation, which means that an add-on library that requests space soon enough could probably get away with allocating up to a few KB without causing any problems. (The slop is not totally useless, since for instance the lock manager might eat it up if more locks get requested than expected.) In the long run it might be interesting to add hooks that allow preloaded libraries to contribute to the shmem sizing calculation and then to snarf up the space they've requested before it can get eaten by the lockmgr. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
