| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Overhead changing varchar(2000) to text |
| Date: | 2015-12-09 23:17:21 |
| Message-ID: | CACjxUsNT7XNpZEpkSQuxykwGG0P-t2A=3y_OfCCjZNpT4K8mxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Dec 9, 2015 at 5:13 PM, Edson Richter <edsonrichter(at)hotmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2015-12-09 23:31:48 | Re: Overhead changing varchar(2000) to text |
| Previous Message | Edson Richter | 2015-12-09 23:13:57 | Overhead changing varchar(2000) to text |