From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] Store Extension Options |
Date: | 2014-03-13 14:28:20 |
Message-ID: | CA+U5nMJwguEj_HhO33m6MdSViLOBDwZs8djuyBAcu_StUo4Mvw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 13 March 2014 13:17, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> In the end, perhaps we should just add another field which is called
> 'custom_reloptions' and allow that to be the "wild west"?
That makes sense.
> ... and allow that to be the "wild west"?
but that would be an emotive phrase that doesn't help acceptance. As
you say, this is just metadata. We have no reason to believe that a
DBA would be less careful with metadata than they are with their data.
We trust them to design their own tables and fill them with data. I
figure we can trust them with options metadata too.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-03-13 14:31:12 | Re: [PATCH] Store Extension Options |
Previous Message | Andres Freund | 2014-03-13 14:27:21 | Re: [PATCH] Store Extension Options |