pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedField wise checking the performance.
2+ messages / 2 participants
[nested] [flat]
* Field wise checking the performance.
@ 2011-02-14 12:06 dba <dbadbb@gmail.com>
0 siblings, 1 reply; 2+ messages in thread
From: dba @ 2011-02-14 12:06 UTC (permalink / raw)
To: pgsql-performance
I have two identical tables. But the with of the fields are different. Need
to know whether changing from varchar(100) to varchar(30) will increase the
performance, or its just the memory access.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Field-wise-checking-the-performance-tp3384348p3384348.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Field wise checking the performance.
@ 2011-02-14 12:30 Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
parent: dba <dbadbb@gmail.com>
0 siblings, 0 replies; 2+ messages in thread
From: Heikki Linnakangas @ 2011-02-14 12:30 UTC (permalink / raw)
To: dba <dbadbb@gmail.com>; +Cc: pgsql-performance
On 14.02.2011 14:06, dba wrote:
> I have two identical tables. But the with of the fields are different. Need
> to know whether changing from varchar(100) to varchar(30) will increase the
> performance, or its just the memory access.
It will make no difference. The max length is just a constraint on what
values can be stored, it doesn't affect how the strings are stored. In
both cases, the strings are stored in a variable-length format.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2011-02-14 12:30 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2011-02-14 12:06 Field wise checking the performance. dba <dbadbb@gmail.com>
2011-02-14 12:30 ` Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox