On Thu, 27 Jan 2005 16:05:09 -0500, Merlin Moncure
> Alexandre wrote:
> > like I'm doing right now, that "de-normalizing" in an array is the way
> > to go.
> Only sometimes. Looping application code is another tactic. There may
> be other things to do as well that don't involve arrays or application
> code. Consider arrays a (very postgresql specific) tool in your
> expanding toolchest.
I take good notes of that. All this opened to me other ways for
solutions, so I'm glad of that. I'll take more time to think about all
> De-normalization is a loaded term because we are only presenting queried
> data in an alternate format (normalization normally applying to data
> structured within the database). There are many people on this list who
> will tell you not to de-normalize anything, ever (and most of the time,
> you shouldn't!).
Thank you for all you help and time for this.
In response to
pgsql-performance by date
|Next:||From: Greg Stark||Date: 2005-01-28 00:14:46|
|Subject: Re: [SQL] OFFSET impact on Performance???|
|Previous:||From: Andrew Sullivan||Date: 2005-01-27 21:36:59|
|Subject: Re: Swapping on Solaris|