Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)

From: Holger Jakobs <holger(at)jakobs(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)
Date: 2020-04-28 09:43:39
Message-ID: cfa5d279-0d2e-38ad-fa7f-3a2788120a83@jakobs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

No, there is no impact.

Am 28.04.20 um 11:22 schrieb Rajin Raj:
> Is there any impact of using the character varying without providing
> the length while creating tables?
> I have created two tables and inserted 1M records. But I don't see any
> difference in pg_class. (size, relpage)
>
> create table test_1(name varchar);
> create table test_2(name varchar(50));
>
> insert into test_1 ... 10M records
> insert into test_2 ... 10M records
>
> vacuum (full,analyze) db_size_test_1;
> vacuum (full,analyze) db_size_test_2;
>
> Which option is recommended?
>
> *Regards,*
> *Rajin *

--
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ashutosh Bapat 2020-04-28 11:46:03 Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)
Previous Message Rajin Raj 2020-04-28 09:22:07 PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleksandr Shulgin 2020-04-28 10:15:36 Re: Proposing WITH ITERATIVE
Previous Message Amit Kapila 2020-04-28 09:41:27 Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions