Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 3748B9FC049 for ; Tue, 5 Jun 2007 10:37:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 87180-01-7 for ; Tue, 5 Jun 2007 10:37:41 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by postgresql.org (Postfix) with ESMTP id 9FC8D9FBE46 for ; Tue, 5 Jun 2007 10:33:43 -0300 (ADT) Received: by ug-out-1314.google.com with SMTP id u2so185461uge for ; Tue, 05 Jun 2007 06:33:41 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=KIJWCvneDkdETlyUO64oCCgNRTfQ2Kh7DFlgib4LRbmDZyshCkImvThbJbSkm9QUnnxjvPhNEjZasPDPXq/cQWBRILOpySd2Zg6BUm+yLwPum8Cwz9hPpzVqLr6ZQu7aLiyI4JQP/qv8APQoVRA0CRMF3CFjxbiIs/R8hRQWa08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=EljUPAY1Zmay4T8LbDiStlE06LG4cZ9jor1P4fXTJmCuT0hcLOgzQiZm3Cfz/6w8DVXGUK/JuZjML0wT1/YLcPxA+CrKdX8VImdEBmz3VTE0OUDhoLw33LBCXXgYBZ41AD4KvfCkVsHxf818M7ct98d16IjgVD7uEtDnYbv+Kao= Received: by 10.78.132.2 with SMTP id f2mr2472500hud.1181050421067; Tue, 05 Jun 2007 06:33:41 -0700 (PDT) Received: by 10.78.201.16 with HTTP; Tue, 5 Jun 2007 06:33:41 -0700 (PDT) Message-ID: <1d219a6f0706050633i47e9724ejc8e8dcc5dbeba2c8@mail.gmail.com> Date: Tue, 5 Jun 2007 09:33:41 -0400 From: "Chris Hoover" To: "pgsql-admin@postgresql.org Admin" Subject: Help with database change MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16016_9568682.1181050421047" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200706/30 X-Sequence-Number: 25698 ------=_Part_16016_9568682.1181050421047 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_16016_9568682.1181050421047 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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
------=_Part_16016_9568682.1181050421047--