Re: pg_guc - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: pg_guc
Date
Msg-id 200306270852.56350.josh@agliodbs.com
Whole thread Raw
In response to Re: pg_guc  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_guc  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_guc  (Aizaz Ahmed <aahmed@redhat.com>)
List pgsql-hackers
Tom,

> Aizaz, if you look at backend/main/main.c it should be pretty obvious
> how to handle this --- it's just like bootstrap mode.  main.c kicks off
> control to GucInfoMain or whatever we call it, and then that routine
> can act pretty much the same as if it were the actual main() of a
> standalone pg_guc.  This also eliminates the need for VARADDR() and a
> lot of the other thrashing about we were doing to allow creation of
> a standalone variable table ... in fact, I think quite a large
> percentage of the patch disappears ...

Are you suggesting putting a copy of the list of GUCs in a system table?  I'd 
be for that ....

-- 
Josh Berkus
Aglio Database Solutions
San Francisco


pgsql-hackers by date:

Previous
From: Thomas Swan
Date:
Subject: Re: Two weeks to feature freeze
Next
From: Tom Lane
Date:
Subject: Re: pg_guc