Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
performance cost for varchar(20), varchar(255), and text - Mailing list pgsql-admin
From
Jessica Richard
Subject
performance cost for varchar(20), varchar(255), and text
Date
July 5, 2008
11:20:02
Msg-id
801541.60585.qm@web56406.mail.re3.yahoo.com
Whole thread
Raw
Responses
Re: performance cost for varchar(20), varchar(255), and text
Re: performance cost for varchar(20), varchar(255), and text
List
pgsql-admin
Tree view
I am tuning a database created by someone else.
I noticed that some column lengths were defined longer than needed.
For example, an Id column is holding a stand length of 20 characters but was defined as varchar(255).
On some other columns, for example, a Description column is supposed to hold less than 100 characters but defined as text.
I am trying to understand the performance impact if a column is over defined in the following cases:
1. char(20) vs varchar(20)
2. varchar(20) vs varchar(255)
3. varchar(255) vs text
thanks,
Jessica
pgsql-admin
by date:
Previous
From:
"Scott Marlowe"
Date:
04 July 2008, 22:24:38
Subject:
Re: How many table scans in a delete...
Next
From:
Shane Ambler
Date:
05 July 2008, 16:28:09
Subject:
Re: performance cost for varchar(20), varchar(255), and text
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies