From: Alexander Staubo <alex@purefiction.net>
To: Fabiola Fernández <fabiola.fg@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: TEXT or LONGTEXT?
Date: Mon, 24 Sep 2007 17:29:48 +0200
Message-ID: <88daf38c0709240829u57361aa9yad96cc2e8dfaa3db@mail.gmail.com> (raw)
In-Reply-To: <66f6273e0709240821j50e89fe6o28c06daf4b0abfc5@mail.gmail.com>
References: <66f6273e0709240821j50e89fe6o28c06daf4b0abfc5@mail.gmail.com>
On 9/24/07, Fabiola Fernández <fabiola.fg@gmail.com> wrote:
> I have a database with an amount of tables and in several of them I have an
> attribute for a semantic definition, for which I use a field of type text. I
> am trying to decide if it would be worth using LONGTEXT instead of TEXT, as
> maybe it would slow down the data insertion and extraction. I hope that you
> could help me. Thank you.
Easy choice -- PostgreSQL does not have a data type named "longtext".
Alexander.
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-performance@postgresql.org
Cc: alex@purefiction.net, fabiola.fg@gmail.com
Subject: Re: TEXT or LONGTEXT?
In-Reply-To: <88daf38c0709240829u57361aa9yad96cc2e8dfaa3db@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