Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Admin > What is the dif...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 3 Topic 4902 of 5123
Post > Topic >>

What is the difference in storage between a blank string and null?

by revoohc@[EMAIL PROTECTED] ("Chris Hoover") Apr 11, 2008 at 04:02 PM

------=_Part_26082_24101719.1207944156311
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm doing some testing on how to decrease our database size as I work on a
partitioning scheme.

I have found that if I have the database store all empty strings as nulls,
I
get a significant savings over saving them as blank strings (i.e. '').
Below is an example of savings I am seeing for the same table:

In my test case, storing empty strings  give me a table size of 20,635,648
Storing empty strings as nulls gives me a table size of: 5,742,592.

As you can see, storing empty strings as nulls is saving me approximately
72% on this table.  So, I am wanting to understand what Postgres is doing
differently with the nulls.  Would someone kindly enlighten me on this.

(P.S. I am using a nullif(trim(column),'') in my partition and view rules
to
store the nulls, and coalesce(column,'') to give my application the data
back without nulls.)

Thanks,

Chris

PG 8.1

-- 
Tired of HIGH Gas prices?  Visit http://colafuelguy.mybpi.com
to start
saving at the pump no matter where you live!

------=_Part_26082_24101719.1207944156311
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I&#39;m doing some testing on how to decrease our database size as I work
on a partitioning scheme.&nbsp; <br><br>I have found that if I have the
database store all empty strings as nulls, I get a significant savings
over saving them as blank strings (i.e. &#39;&#39;).&nbsp; Below is an
example of savings I am seeing for the same table:<br>
<br>In my test case, storing empty strings&nbsp; give me a table size of
20,635,648<br><meta http-equiv="CONTENT-TYPE" content="text/html;
charset=utf-8"><title></title><meta name="GENERATOR"
content="OpenOffice.org 2.4  (Linux)">Storing empty strings as nulls gives
me a table size of: 5,742,592.<br>
<br>As you can see, storing empty strings as nulls is saving me
approximately 72% on this table.&nbsp; So, I am wanting to understand what
Postgres is doing differently with the nulls.&nbsp; Would someone kindly
enlighten me on this.<br>
<br>(P.S. I am using a nullif(trim(column),&#39;&#39;) in my partition and
view rules to store the nulls, and coalesce(column,&#39;&#39;) to give my
application the data back without nulls.)<br><br>Thanks,<br><br>Chris<br>
<br>PG 8.1<br clear="all"><br>-- <br>Tired of HIGH Gas prices?&nbsp; Visit
<a href="http://colafuelguy.mybpi.com">http://colafuelguy.mybpi.com</a>
to
start saving at the pump no matter where you live!<br>

------=_Part_26082_24101719.1207944156311--




 3 Posts in Topic:
What is the difference in storage between a blank string and nul
revoohc@[EMAIL PROTECTED]  2008-04-11 16:02:36 
Re: What is the difference in storage between a blank
ktm@[EMAIL PROTECTED] (K  2008-04-11 16:24:40 
Re: What is the difference in storage between a blank string
pgsql@[EMAIL PROTECTED]   2008-04-12 14:44:34 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan13V112 Fri Jul 4 14:41:06 CDT 2008.