| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Order of views in stats docs |
| Date: | 2014-11-05 21:59:38 |
| Message-ID: | 545A9DCA.6010608@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/5/14, 2:43 PM, Peter Eisentraut wrote:
> On 11/5/14 10:57 AM, Tom Lane wrote:
>> However, should we consider the possibility of changing the table to
>> straight alphabetical ordering? I'm not as much in love with that
>> approach as some folks, but it does have the merit that it's always clear
>> where you ought to put a new item.
>
> Yes, I think that property is important when developing in a loose
> community.
Couldn't we just stick a warning SGML comment at the end of the list? ISTM that's no more likely to be missed/ignored than noticing that the list happens to be alphabetical.
Perhaps the best solution is to split the list into different areas; one for database stats, another for table stats, etc.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2014-11-05 22:05:34 | Re: Amazon Redshift |
| Previous Message | Kevin Grittner | 2014-11-05 21:42:15 | Re: Amazon Redshift |