pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Hoover <revoohc@gmail.com>
To: pgsql-admin@postgresql.org Admin <pgsql-admin@postgresql.org>
Subject: Help with database change
Date: Tue, 5 Jun 2007 09:33:41 -0400
Message-ID: <1d219a6f0706050633i47e9724ejc8e8dcc5dbeba2c8@mail.gmail.com> (raw)

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

view thread (2+ messages)  latest in thread

Message-ID: <1d219a6f0706050633i47e9724ejc8e8dcc5dbeba2c8@mail.gmail.com>
Permalink:  ../1d219a6f0706050633i47e9724ejc8e8dcc5dbeba2c8@mail.gmail.com/
Also on:    postgresql.org/message-id/1d219a6f0706050633i47e9724ejc8e8dcc5dbeba2c8@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: revoohc@gmail.com
  Subject: Re: Help with database change
  In-Reply-To: <1d219a6f0706050633i47e9724ejc8e8dcc5dbeba2c8@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox