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

Re: generic reloptions improvement

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Subject: Re: generic reloptions improvement
Date: 2008-12-29 03:26:36
Message-ID: 20081229032636.GC5035@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:

> > I'm intending to have a new routine which would reserve a value at
> > runtime.  This value would be later be passed by the AM to create new
> > options on the table.
> 
> What do you mean by "at runtime"?  Surely the value would have to remain
> stable across database restarts, since it's going to relate to stuff
> that is in catalog entries.

No, there's no need for the value to be stable across restart; what's
stored in catalogs is the option name, which is linked to the kind
number only in the parser table.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-hackers by date

Next:From: Hitoshi HaradaDate: 2008-12-29 04:18:35
Subject: Re: Windowing Function Patch Review -> Standard Conformance
Previous:From: Devrim GÜNDÜZDate: 2008-12-28 23:43:31
Subject: Re: Re: [COMMITTERS] pgsql: SQL/MED catalog manipulationfacilities This doesn't do any

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