Skip site navigation (1) Skip section navigation (2)

Re: pg_guc

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Fernando Nasser <fnasser(at)redhat(dot)com>,Aizaz Ahmed <aahmed(at)redhat(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_guc
Date: 2003-06-27 15:52:56
Message-ID: 200306270852.56350.josh@agliodbs.com (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-06-27 15:59:36
Subject: Re: pg_guc
Previous:From: Thomas SwanDate: 2003-06-27 15:43:04
Subject: Re: Two weeks to feature freeze

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group