From: | "Chris Hoover" <revoohc(at)gmail(dot)com> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org Admin" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Help with database change |
Date: | 2007-06-05 13:33:41 |
Message-ID: | 1d219a6f0706050633i47e9724ejc8e8dcc5dbeba2c8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I am doing some research into partitioning my postgres database. While
doing this, I am trying to take the opportunity to improve the over all
database.design. One of the things I am thinking of implementing would be
the use of nullif/coalesce. Our application tends to send a lot of strings
that only contain spaces. While I know in the long run, the application
needs to be fixed, I was thinking about using nullif and coalesce so the
database can just store nulls in the database and save the space of storing
"empty" strings as an interim fix.
My question is, how expensive is nullif and coalesce? Can I expect to see a
noticeable impact on performance if I do this?
Thanks,
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Marc Cousin | 2007-06-05 14:06:04 | about threaded libpq |
Previous Message | Andrew Sullivan | 2007-06-05 13:25:46 | Re: the right time to vacuum database? |