Simon Riggs <[EMAIL PROTECTED]> writes:
> This was a response to Itagaki's comment that there may be a class of
> parameter that changes more frequently than that. I can see that we
> might want that, so just trying to plan ahead to
> dynamically/automatically set parameters - I thought you'd be in
On Mon, 2006-06-19 at 09:15 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Looks like we've got a class of data that is similar in its frequency of
> > change to the pg_class_nt stuff.
>
> Say what? These parameters wouldn't ever change after creation, unless
> we invent ALT
Simon Riggs <[EMAIL PROTECTED]> writes:
> Looks like we've got a class of data that is similar in its frequency of
> change to the pg_class_nt stuff.
Say what? These parameters wouldn't ever change after creation, unless
we invent ALTER commands to change them.
regards, t
I propose a patch to make pg_regress.sh more modular. I'd like to do
ecpg regression tests for my soc project and don't want to duplicate
functionality. I put those parts of the code that parse the command line
and set up the environment variables and the database into sh-functions
and moved them t
On Mon, 2006-06-19 at 14:36 +0900, ITAGAKI Takahiro wrote:
> Simon Riggs <[EMAIL PROTECTED]> wrote:
>
> > > 2. Store the structures in AM's meta page. But heaps don't have meta
> > > pages.
> >
> > But perhaps they should? That sounds very similar to the idea of
> > non-transactional pg_class d
