| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 9.4 Proposal: Initdb creates a single table |
| Date: | 2014-04-23 11:46:22 |
| Message-ID: | 5357A80E.70908@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
This seems like a much better idea - whereas a single table, related to
nothing - on the other hand, is at best not very helpful (and it could
be argued, might contribute to teaching poor data data design).
Regards
Mark
On 23/04/14 19:13, Pavel Stehule wrote:
> Hello
>
> if you are thinking about this direction, then store there some demo
> project.
>
> I am don't think so isolated table has significant price.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2014-04-23 12:17:49 | Re: Re: default opclass for jsonb (was Re: Call for GIST/GIN/SP-GIST opclass documentation) |
| Previous Message | Simon Riggs | 2014-04-23 11:39:37 | Re: 9.4 Proposal: Initdb creates a single table |