Tom Lane wrote: > After looking at the code a bit, I think the simplest solution is for > find_option to look in a separate mapping table (mapping from old to new > option name) if it doesn't find the given name in the main table. This > would make lookup of "old" names a shade slower than "preferred" names, > but that doesn't seem like a problem. > > With this approach, old GUC names would be recognized in SHOW and SET > commands, as well as the other ways you can set a variable by name > (postgresql.conf, ALTER USER SET, etc). But only the new names would > appear in SHOW ALL or the pg_settings view. Does that seem OK?
Sounds good. The idea that we can keep the names constant seems to be a losing proposal. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
