On Sun February 5 2006 16:16, Tom Lane wrote: > AFAICT the data structures you are worried about don't have any readily > predictable size, which means there is no good way to keep them in > shared memory --- we can't dynamically resize shared memory. So I think > storing the rules in a table and loading into private memory at need is > really the only reasonable solution. Storing them in a table has a lot > of other advantages anyway, mainly that you can manipulate them from > SQL.
I have come to the conclusion that storing the rules and various other bits in tables is the best solution, although this will require a much more complex db structure than I had originally planned. Trying to allocate and free memory in shared memory is fairly straightforward, but likely to become incredibly messy. Seeing as some of the rules already include load-value-from-db-on-demand, it should be fairly straightforward to extend it to load-rule-from-db-on-demand. Thanks for all your help, Regards, Richard ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
