[EMAIL PROTECTED] writes:
> Hello i would like to know if not determining a max size value for a
> character varying's fields decrease the perfomance (perhaps size of
> stockage ?
No, more the other way around: specifying varchar(N) when you had to
pick N out of the air decreases performance, beca
On lau, 2007-06-16 at 13:35 +0200, [EMAIL PROTECTED] wrote:
> Thanks
>
> if i understand well that means that if i choose character varying(3) or
> character varying(8) or character varying(32) or character varying with no max
> length the fields will take the same place in the disk (8kb) except f
Thanks
if i understand well that means that if i choose character varying(3) or
character varying(8) or character varying(32) or character varying with no max
length the fields will take the same place in the disk (8kb) except for fields
too long to take place in the 8kb whose are stored in anothe
[EMAIL PROTECTED] <[EMAIL PROTECTED]> schrieb:
> Hello i would like to know if not determining a max size value for a character
> varying's fields decrease the perfomance (perhaps size of stockage ? or
> something else ?)
No problem because of the TOAST-technology:
http://www.postgresql.org/docs/
Hello i would like to know if not determining a max size value for a character
varying's fields decrease the perfomance (perhaps size of stockage ? or
something else ?)
If not it is a good way to not specify a max size value ?
If it has an importance is it possible to have a general environnment v
