pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedCan't find docs on Postgresql.conf
12+ messages / 4 participants
[nested] [flat]
* Can't find docs on Postgresql.conf
@ 2001-11-06 23:06 Josh Berkus <josh@agliodbs.com>
0 siblings, 2 replies; 12+ messages in thread
From: Josh Berkus @ 2001-11-06 23:06 UTC (permalink / raw)
To: pgsql-sql
Folks,
I know there are full docs on postgresql.org somewhere detailing all of
the postgresql.conf options. I can't find them ... only the limited set
in the "runtime options" section.
I'm looking for the option to change the number of parameters allowed
for functions.
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-06 23:42 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Josh Berkus <josh@agliodbs.com>
1 sibling, 1 reply; 12+ messages in thread
From: Bruce Momjian @ 2001-11-06 23:42 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql
> Folks,
>
> I know there are full docs on postgresql.org somewhere detailing all of
> the postgresql.conf options. I can't find them ... only the limited set
> in the "runtime options" section.
>
> I'm looking for the option to change the number of parameters allowed
> for functions.
I don't think we have a configure option for the number of parameters.
The number of params and the length of identifiers are two things we
should increase in 7.3.
In TODO we now have:
* Increase identifier length (NAMEDATALEN) if small performance hit
* Increase maximum number of function parameters
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 00:10 Tom Lane <tgl@sss.pgh.pa.us>
parent: Josh Berkus <josh@agliodbs.com>
1 sibling, 0 replies; 12+ messages in thread
From: Tom Lane @ 2001-11-07 00:10 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-sql
"Josh Berkus" <josh@agliodbs.com> writes:
> I know there are full docs on postgresql.org somewhere detailing all of
> the postgresql.conf options. I can't find them ... only the limited set
> in the "runtime options" section.
> I'm looking for the option to change the number of parameters allowed
> for functions.
You're not finding it there because that's not where it is ;-)
You need to change config.h and rebuild and re-initdb, instead.
regards, tom lane
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 00:17 Tom Lane <tgl@sss.pgh.pa.us>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 12+ messages in thread
From: Tom Lane @ 2001-11-07 00:17 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-sql
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> The number of params and the length of identifiers are two things we
> should increase in 7.3.
> In TODO we now have:
> * Increase identifier length (NAMEDATALEN) if small performance hit
> * Increase maximum number of function parameters
We already *did* increase the standard max number of function
parameters, from 8 to 16, and that was just a couple or three versions
back. I don't recall hearing any groundswell of complaints to evidence
that very many people need it set higher.
NAMEDATALEN is a different story --- we do see complaints about that
fairly regularly.
regards, tom lane
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 00:21 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 12+ messages in thread
From: Bruce Momjian @ 2001-11-07 00:21 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-sql
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > The number of params and the length of identifiers are two things we
> > should increase in 7.3.
>
> > In TODO we now have:
>
> > * Increase identifier length (NAMEDATALEN) if small performance hit
> > * Increase maximum number of function parameters
>
> We already *did* increase the standard max number of function
> parameters, from 8 to 16, and that was just a couple or three versions
> back. I don't recall hearing any groundswell of complaints to evidence
> that very many people need it set higher.
I was talking to Ben Adida last week (OpenACS) and he mentioned they are
having problems with the limit at 16, and it seems Josh is as well. Ben
is doing some object-oriented function mechanism, and you know how that
can eat parameters. Seems we should increase to 24 or 32. Is there a
downside to the increase. I can't even imagine a performance hit.
Comments?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 00:26 Tom Lane <tgl@sss.pgh.pa.us>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
1 sibling, 1 reply; 12+ messages in thread
From: Tom Lane @ 2001-11-07 00:26 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-sql
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Seems we should increase to 24 or 32. Is there a
> downside to the increase. I can't even imagine a performance hit.
Darn if I know. We should try to measure it before assuming it's
insignificant. At the very least, it'd increase the size of pg_proc
by about a third ...
regards, tom lane
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 00:28 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 12+ messages in thread
From: Bruce Momjian @ 2001-11-07 00:28 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-sql
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Seems we should increase to 24 or 32. Is there a
> > downside to the increase. I can't even imagine a performance hit.
>
> Darn if I know. We should try to measure it before assuming it's
> insignificant. At the very least, it'd increase the size of pg_proc
> by about a third ...
Doesn't it store in pg_proc as an array, which is of variable length?
I think the only overhead is adding code to fmgr.c for the extra param
combinations.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 00:45 Tom Lane <tgl@sss.pgh.pa.us>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 2 replies; 12+ messages in thread
From: Tom Lane @ 2001-11-07 00:45 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-sql
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Doesn't it store in pg_proc as an array, which is of variable length?
No, it's *fixed* length. Increasing FUNC_MAX_ARGS translates directly
to wasted space.
regards, tom lane
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 01:32 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 12+ messages in thread
From: Bruce Momjian @ 2001-11-07 01:32 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-sql
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Doesn't it store in pg_proc as an array, which is of variable length?
>
> No, it's *fixed* length. Increasing FUNC_MAX_ARGS translates directly
> to wasted space.
Oh, I see it now, it is our old friend 'oidvector'. Now I remember
modifying that when we changed from 8 to 16.
I have modified the TODO to say:
* Increase maximum number of function parameters if little
wasted space
We can address this during 7.3. and decide if it is worth it. Maybe it
isn't. My calculations show a change of proc params from 16 to 32
would increase tuple length for pg_proc change from 180 to 244 or a 35%
increase.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-07 01:47 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 12+ messages in thread
From: Bruce Momjian @ 2001-11-07 01:47 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Josh Berkus <josh@agliodbs.com>; pgsql-sql
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Doesn't it store in pg_proc as an array, which is of variable length?
>
> No, it's *fixed* length. Increasing FUNC_MAX_ARGS translates directly
> to wasted space.
If we increase it from 16 to 24, that changes from 180 to 212 or a 17%
increase. That may be a reasonable default.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-08 00:40 Roberto Mello <rmello@cc.usu.edu>
parent: Bruce Momjian <pgman@candle.pha.pa.us>
1 sibling, 1 reply; 12+ messages in thread
From: Roberto Mello @ 2001-11-08 00:40 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Josh Berkus <josh@agliodbs.com>; pgsql-sql
On Tue, Nov 06, 2001 at 07:21:09PM -0500, Bruce Momjian wrote:
>
> I was talking to Ben Adida last week (OpenACS) and he mentioned they are
> having problems with the limit at 16, and it seems Josh is as well. Ben
> is doing some object-oriented function mechanism, and you know how that
> can eat parameters. Seems we should increase to 24 or 32. Is there a
> downside to the increase. I can't even imagine a performance hit.
Indeed we (at OpenACS) could use more parameters.
We are porting a zillion Oracle PL/SQL functions to Postgres, and in
Oracle you can have optional parameters and default values. In PostgreSQL
we have to overload functions to make up for the possible combinations.
In this process, sometimes we run out of parameters and have to submit to
more, errr, creative ways to get the job done.
The %TYPE patch that was added to 7.2 will help us a lot. Thanks a bunch.
-Roberto
--
+----| http://fslc.usu.edu USU Free Software & GNU/Linux Club |------+
Roberto Mello - Computer Science, USU - http://www.brasileiro.net
http://www.sdl.usu.edu - Space Dynamics Lab, Developer
Error finding REALITY.SYS - Universe halted.
^ permalink raw reply [nested|flat] 12+ messages in thread
* Re: Can't find docs on Postgresql.conf
@ 2001-11-08 02:36 Bruce Momjian <pgman@candle.pha.pa.us>
parent: Roberto Mello <rmello@cc.usu.edu>
0 siblings, 0 replies; 12+ messages in thread
From: Bruce Momjian @ 2001-11-08 02:36 UTC (permalink / raw)
To: Roberto Mello <rmello@cc.usu.edu>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Josh Berkus <josh@agliodbs.com>; pgsql-sql
> On Tue, Nov 06, 2001 at 07:21:09PM -0500, Bruce Momjian wrote:
> >
> > I was talking to Ben Adida last week (OpenACS) and he mentioned they are
> > having problems with the limit at 16, and it seems Josh is as well. Ben
> > is doing some object-oriented function mechanism, and you know how that
> > can eat parameters. Seems we should increase to 24 or 32. Is there a
> > downside to the increase. I can't even imagine a performance hit.
>
> Indeed we (at OpenACS) could use more parameters.
>
> We are porting a zillion Oracle PL/SQL functions to Postgres, and in
> Oracle you can have optional parameters and default values. In PostgreSQL
> we have to overload functions to make up for the possible combinations.
>
> In this process, sometimes we run out of parameters and have to submit to
> more, errr, creative ways to get the job done.
Good. Will 24 params be enough for you?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 12+ messages in thread
end of thread, other threads:[~2001-11-08 02:36 UTC | newest]
Thread overview: 12+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-11-06 23:06 Can't find docs on Postgresql.conf Josh Berkus <josh@agliodbs.com>
2001-11-06 23:42 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-11-07 00:17 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-11-07 00:21 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-11-07 00:26 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-11-07 00:28 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-11-07 00:45 ` Tom Lane <tgl@sss.pgh.pa.us>
2001-11-07 01:32 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-11-07 01:47 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-11-08 00:40 ` Roberto Mello <rmello@cc.usu.edu>
2001-11-08 02:36 ` Bruce Momjian <pgman@candle.pha.pa.us>
2001-11-07 00:10 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox