Postgres Pro
Downloads
Home   >   mailing lists

PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) - Mailing list pgsql-admin

From Rajin Raj
Subject PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)
Date
Msg-id CAOasRJYCUwMYdd=BL29TupW_iCbvM3YRM01YTB_WYSUEays3CA@mail.gmail.com
Whole thread Raw
Responses Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)  (Holger Jakobs <holger@jakobs.com>)
Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)  (Paul Carlucci <paul.carlucci@gmail.com>)
Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)  (Paul Carlucci <paul.carlucci@gmail.com>)
List pgsql-admin
Tree view
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 

pgsql-admin by date:

Previous
From: Rui DeSousa
Date:
Subject: Re: PostgreSQL DB checkpoint error!
Next
From: Holger Jakobs
Date:
Subject: Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length)