Skip site navigation (1) Skip section navigation (2)

Re: Making oidvector and int2vector variable-length

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Making oidvector and int2vector variable-length
Date: 2005-03-28 16:57:58
Message-ID: 200503280857.58845.josh@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Alvaro, Tom,

> > Very likely we could kick it up to 100 or so without feeling any pain;
> > how high were you thinking?
>
> I used to see people asking to raise it to 64 or so.  Not sure if it
> would be useful to go higher than that ... much less now that we have
> full-fledged support for row types.

Actually, I'm right now working on a function with 88 parameters, which have 
to be passed through a temp table in 7.4.   I've seen Oracle PL/SQL 
procedures with 140 parameters.   While it's possible to work around this 
using row types, it's cumbersome, and extremely painful if you're porting an 
application.  

So if we can make this variable-length, I'd say set the limit at 400 to avoid 
TOASTing, but otherwise allow users as many parameters as they want.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2005-03-28 17:11:34
Subject: Re: [PATCHES] Patch for database locale settings
Previous:From: Frank L. ParksDate: 2005-03-28 16:44:43
Subject: Re: is postgresql 8 is realy mature

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group