From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Thomas Hallgren <thhal(at)mailblocks(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GUC variable set, TODO |
Date: | 2004-04-19 15:44:38 |
Message-ID: | Pine.LNX.4.58.0404191730390.6454@sablons.cri.ensmp.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Tom,
> > . All guc variables are described in static structures initialized at
> > loadtime. if it is to be extendable, it means that you have break this,
>
> No, you don't.
Well, sorry, I'm used to show my lack of imagination on the list;-)
> > . There is also a dynamic sorted array that allows to find all variables
> > descriptions independently of their type, with a binary search.
>
> The idea was to provide an API that would allow insertion of new entries
> into the dynamic array. This does not mean you have to reinvent where
> the static entries come from.
Ok. I understand that you suggest to Thomas that he should only touch
the search array to insert new pointers to guc description structures,
which may come from outside or be newly allocated, without touching the
existing static versions for internal guc variables.
--
Fabien Coelho - coelho(at)cri(dot)ensmp(dot)fr
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-04-19 16:00:10 | Re: query slows down with more accurate stats |
Previous Message | Tom Lane | 2004-04-19 15:25:08 | Re: GUC variable set, TODO |