Re: Overhead changing varchar(2000) to text - Mailing list pgsql-general

From Kevin Grittner
Subject Re: Overhead changing varchar(2000) to text
Date
Msg-id CACjxUsNT7XNpZEpkSQuxykwGG0P-t2A=3y_OfCCjZNpT4K8mxQ@mail.gmail.com
Whole thread Raw
In response to Overhead changing varchar(2000) to text  (Edson Richter <edsonrichter@hotmail.com>)
Responses Re: Overhead changing varchar(2000) to text
Re: Overhead changing varchar(2000) to text
List pgsql-general
On Wed, Dec 9, 2015 at 5:13 PM, Edson Richter <edsonrichter@hotmail.com> wrote:

> I do have several tables that uses varchar(2000) as store for remarks.
> Lately, one customer need to store more than 2000 characteres, and I'm
> considering changing from varchar(2000) to text.
>
> What is the overhead?

None -- they are stored in exactly the same format; the only
difference is whether the length is limited.

> Is there any place where I can learn about storage impacto for each data
> type?

http://www.postgresql.org/docs/current/interactive/datatype-character.html

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-general by date:

Previous
From: Edson Richter
Date:
Subject: Overhead changing varchar(2000) to text
Next
From: Kevin Grittner
Date:
Subject: Re: Overhead changing varchar(2000) to text