Re: Maximum size for char or varchar with limit

From: Jasen Betts <jasen(at)xnet(dot)co(dot)nz>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Maximum size for char or varchar with limit
Date: 2010-12-19 10:07:26
Message-ID: ieklgu$ql1$2@reversiblemaps.ath.cx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2010-12-08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

I have some values of perhaps 20Mb that I might want to store samples
of in a partitioned table. (so I can delete them easily) what's the right way?

I guess I could just keep them as disk files and rotate the
directories as I rotate partitions.

--
⚂⚃ 100% natural

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Oleg Bartunov 2010-12-19 12:52:43 Re: FTS phrase searches
Previous Message Jasen Betts 2010-12-19 09:51:32 Re: INSERT INTO...RETURNING with partitioned table based on trigger function