| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Fabrízio Mello <fabriziomello(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Store Extension Options |
| Date: | 2014-01-02 09:19:54 |
| Message-ID: | 20140102091954.GG2683@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-12-31 13:37:59 +0100, Pavel Stehule wrote:
> > We use the namespace "ext" to the internal code
> > (src/backend/access/common/reloptions.c) skip some validations and store
> > the custom GUC.
> >
> > Do you think we don't need to use the "ext" namespace?
> >
>
> yes - there be same mechanism as we use for GUC
There is no existing mechanism to handle conflicts for GUCs. The
difference is that for GUCs nearly no "namespaced" GUCs exist (plperl,
plpgsql have some), but postgres defines at least autovacuum. and
toast. namespaces for relation options.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-01-02 09:27:57 | Re: Show lossy heap block info in EXPLAIN ANALYZE for bitmap heap scan |
| Previous Message | Andres Freund | 2014-01-02 09:17:45 | Re: proposal: multiple read-write masters in a cluster with wal-streaming synchronization |