I can see how schemas can be used to keep related tables and other object together. I may be missing something but I don't see how they can be used to emulate the "once-per-session" behavior of Oracle packages. Have I missed something?
There is nothing similar in Postgres.
I am working session variables, that should be created in schema too. As workaround you can use GUC - configuration variables, that can be used for storing private values too.
One of the nice things about Oracle packages is that the code is loaded and global values are set and stored only once per session. This is very useful for values that are used repeatedly.
What is the best way of emulating this behavior in Postgresql?
