| From: | Θάνος Παπαπέτρου <thanos(at)di(dot)uoa(dot)gr> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | GUC configuration |
| Date: | 2011-02-10 13:17:34 |
| Message-ID: | 066A2B5F-2CC4-4282-93F0-0BDF8797CE27@di.uoa.gr |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 some new cost models for DB optimizers. I have
successfully changed the optimizer of PostgreSQL in order to implement
these models, 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 is about configuring existing PostgreSQL variables. Can
anybody please provide some help? How can I add some new configuration
variables using GUC?
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2011-02-10 14:03:23 | Re: 9.0.X FOR UPDATE|SHARE on Sub-Query Causes "cannot extract system attribute from virtual tuple" if Sub-Query Returns Records (BUG) |
| Previous Message | Gerd Koenig | 2011-02-10 10:02:32 | partitioning and dynamic query creation |