From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: renaming "storage parameters" |
Date: | 2009-02-09 18:09:16 |
Message-ID: | 18391.1234202956@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Euler Taveira is arguing in an autovacuum thread that we should give
> "storage parameters" a different name; his argument is that
> "autovacuum_enabled" is not really a parameter that relates to storage.
> He is proposing "relation parameters".
> I am against the idea of renaming them, for two reasons: 1. it's a
> user-visible change that doesn't seem to buy a lot; 2. it's a tedious
> patch to write.
> Can I get some votes?
I agree with leaving them alone. "Storage" might not be exactly le mot
juste anymore but it still gives you a good idea what they're meant for;
in particular that they are targeted at implementation concerns rather
than SQL-level semantics of the table. Moving to a content-free name
like "relation parameter" in order to cover all possible uses doesn't
seem like it helps anyone understand anything better.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-02-09 18:28:32 | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
Previous Message | Tom Lane | 2009-02-09 18:02:35 | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |