Re: Best practices for aggregate table design - Mailing list pgsql-general

From David G. Johnston
Subject Re: Best practices for aggregate table design
Date
Msg-id CAKFQuwa5ToyFKp5eP=ng0G=Pbe-Qo2pVdgY8D2j1i_V304_+6Q@mail.gmail.com
Whole thread Raw
In response to Re: Best practices for aggregate table design  (droberts <david.roberts@riverbed.com>)
Responses Re: Best practices for aggregate table design  (droberts <david.roberts@riverbed.com>)
List pgsql-general
Nabble has a "quote" feature - please use it.

On Thu, Oct 8, 2015 at 5:00 PM, droberts <david.roberts@riverbed.com> wrote:
I haven't but wouldn't it be better to wait and just add new columns if/when
I need to?

​Its worth keeping in the back of your mind but I tend to think that choosing hstore in order to "be flexible" is a solution looking for a problem.  The dynamics between your system and the source system will play a large role in determining whether to use a mini-table-within-a-table in your model.

David J.

pgsql-general by date:

Previous
From: droberts
Date:
Subject: Re: Best practices for aggregate table design
Next
From: Jeff Janes
Date:
Subject: Version management for extensions