Re: per-column generic option - Mailing list pgsql-hackers

From Robert Haas
Subject Re: per-column generic option
Date
Msg-id BANLkTi=LtNQCK3ARa4_aGzfE+Pzhw0AfVQ@mail.gmail.com
Whole thread Raw
In response to Re: per-column generic option  (Shigeru Hanada <shigeru.hanada@gmail.com>)
List pgsql-hackers
2011/6/27 Shigeru Hanada <shigeru.hanada@gmail.com>:
>> * It might be an option to extend attreloptions, instead of the new
>> attfdwoptions.
>> Although I didn't track the discussion when pg_foreign_table catalog
>> that provides
>> relation level fdw-options, was it impossible or unreasonable to extend existing
>> design of reloptions/attoptions?
>> Right now, it accepts only hard-wired options listed at reloptions.c.
>> But, it seems
>> to me worthwhile, if it could accept options validated by loadable modules.
>
> IIRC someone has objected against storing FDW options in
> reloptions/attoptions, but I couldn't find such post.  I'll follow the
> discussion again.

I think they should definitely be separate.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_upgrade defaulting to port 25432
Next
From: "David E. Wheeler"
Date:
Subject: Re: generate_series() Interpretation