From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org, Rob Gansevles <rgansevles(at)gmail(dot)com> |
Subject: | Re: Maximum size for char or varchar with limit |
Date: | 2010-12-08 17:05:18 |
Message-ID: | 16864.1291827918@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> On 12/08/2010 08:04 AM, Tom Lane wrote:
>> The rationale for having a limit of this sort is (a) we *don't* want
>> the upper limit of declarable length to be encoding-dependent; and
>> (b) if you are trying to declare an upper limit that's got more than a
>> few digits in it, you almost certainly ought to not be declaring a limit
>> at all.
> Well that explains it :) Would it be possible to change the below
> section in the docs to state that the declared max value of n is limited
> to a max string size of 10Mb?
I don't really see any point in that. The value is meant to be an order
of magnitude or so more than anything that's sane according to point (b).
If you think you need to know what it is, you're already doing it wrong.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2010-12-08 17:12:05 | Re: Maximum size for char or varchar with limit |
Previous Message | Gabi Julien | 2010-12-08 16:37:51 | Re: Postgresql 9.1 pg_last_xact_replay_timestamp limitations |