Re: size of function body - Mailing list pgsql-general

From Ralph Graulich
Subject Re: size of function body
Date
Msg-id Pine.LNX.4.21.0207162358340.9511-100000@shauny.shauny.de
Whole thread Raw
In response to Re: size of function body  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: size of function body  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi Tom,


> Hmm.  Are there any long literal strings in your function text?

Sorry for asking more questions to track down the problem:

What exactly do you mean by "long literal string"? Does it mean the length
of a variable name or the length of the content of a variable?

The longest variable names are:

running_total_of_coverings_by_same_family_sire
running_total_of_coverings_by_different_family_sire
running_total_of_active_breeding_years

But only used three or four times.

But I do concatenating of string lots of time within the code, which means
I store several derived variable contents into one single variable and put
that in a TEXT field in an UPDATE statement. Can this cause the problem
you described?

Nonetheless I am willing to try the patch, for sure!


Kind regards
... Ralph ...



pgsql-general by date:

Previous
From: "Johnson, Shaunn"
Date:
Subject: replicating database
Next
From: Tom Lane
Date:
Subject: Re: size of function body