Re: varchar vs. text + constraint/triggers was: Help request to improve function performance

From: Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>
To: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: varchar vs. text + constraint/triggers was: Help request to improve function performance
Date: 2009-04-23 11:50:42
Message-ID: 2f4958ff0904230450pb8cd1a8q32db1d09958ce946@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

essentially you are trying to store a database in a database, and
that's slow for one.
Second, storing things as varchar is space and index (space)
ineffective - and that's another reason to make things slower.
Third - you need to complicate your logic to retrieve data, and that adds up.

text is less of hassle for db, true - but that's just a tip of iceberg.

Just learn to create proper database schema, and make it so it meets
your criteria - otherwise , whatever else you choose - especially
'automatic' 'intelligent' isn't going to be ever as good as proper
schema.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2009-04-23 11:57:46 Re: varchar vs. text + constraint/triggers was: Help request to improve function performance
Previous Message Ivan Sergio Borgonovo 2009-04-23 11:21:05 Re: varchar vs. text + constraint/triggers was: Help request to improve function performance