From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | <mel(at)gmanmi(dot)tv>, "'Ron Johnson'" <ron(dot)l(dot)johnson(at)cox(dot)net>, "'PgSQL Novice ML'" <pgsql-novice(at)postgresql(dot)org>, "'Dani Oderbolz'" <oderbolz(at)ecologic(dot)de> |
Subject: | Re: sql question (hopefully) |
Date: | 2003-06-18 15:13:30 |
Message-ID: | 200306180813.30095.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Mel,
> i wanted to find out for sure if i really won't get the desired result(s)
> in sql and have to create a function instead.
Perhaps, but the function better be in C, or your performance will continue to
suck ...
> yes it breaks the 1st normal form. we did this for some *practical*
> purposes supposedly. =) i would've wanted to discuss it here but i'll
> probably bore you to death or i'd end up starting a new discussion
> altogether. since it's in production and i need to do a quick patch
> without touching the external programs depending on this schema, i've to
> find a quick remedy.
To be frank, boyo, you're on the road to hell.
I am constantly amazed at how many newbie DBAs adopt not-normalized schema
because "it's faster" and then have to add in workarounds that kill the
performance of their database.
Anyway, if someone else doesn't solve it, I'll come up with a SQL solution
later in the week ....
--
Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Fontenot, Paul | 2003-06-18 16:16:50 | Vacuum and inserts |
Previous Message | Mel Jamero | 2003-06-18 14:40:49 | Re: sql question (hopefully) |