Hi,

I am an MSc student in the department of Informatics and Telecommunications of the University of Athens and as part of my thesis I am examining a new path/plan cost model for DB optimizers. I have successfully changed the optimizer of PostgreSQL in order to implement this model, but I have stumbled upon a very little detail: until now I use some hardcoded values in my code which I would like to make accessible through GUC. After much googling the only relative pages I have found are about configuring existing PostgreSQL variables and src/backend/utils/misc/README does not mention anything about adding new vars. Can anybody please provide some help?

I presume I have to add new entries in ConfigureNames* arrays in src/ backend/utils/misc/guc.c, but I am not sure about the field values of config_* structs I have to enter. Also is there any "standard" location where the actual variables should be declared, or I can freely declare them in any source file (the source file that actually uses them)? Do I have to declare a config_generic struct too? How do I specify boot values?

Thanks in advance,

Thanos Papapetrou

Θάνος Παπαπέτρου

You insist that there is something that a machine can't do. If you will tell me precisely what it is that a machine cannot do, then I can always make a machine which will do just that.

P.S.: I initially posted this message in pgsql-generic, but after thinking about it more I believe this is the most appropriate list, so I re-posted here.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to