[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] varchar(n) VS text
From:       Tom Lane <tgl () sss ! pgh ! pa ! us>
Date:       2007-06-30 0:09:58
Message-ID: 10066.1183162198 () sss ! pgh ! pa ! us
[Download RAW message or body]

Kev <kevinjamesfield@gmail.com> writes:
> On Jun 26, 12:16 am, t...@sss.pgh.pa.us (Tom Lane) wrote:
>> "Pierre Thibaudeau" <pierd...@gmail.com> writes:
>>> I am puzzling over this issue:
>>> 1) Is there ever ANY reason to prefer "varchar(n)" to "text" as a column type?
>> 
>> In words of one syllable: no.

> If you have any input from untrusted sources (like in a web app)
> wouldn't it be easier to attack the server if you had a text field,
> like by sending a couple TB of data over that pgsql then needs to
> store, on a server that doesn't have that amount of space?

Well, the hard limit on a text field (or any other field) is 1Gb,
so it'd not be quite as easy as that, even assuming that the webapp
doesn't fall over first.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

               http://archives.postgresql.org/
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic