Re: Prepared Statement Name Truncation

Phil Sorber <phil@omniti.com> writes:
> An install of ours was having an issue with log files filling up the
> disk rather quickly. After looking into it, the log was filling up
> with NOTICE's caused by an ORM that was using a very long identifier
> as a name for a prepared statement. It was a concatenation of tables
> in the query.

Just to be clear here ... does this ORM expect that it can concatenate
*any* two legal identifiers into another one?  If so, it's going to be
broken no matter what the specific length limit is.

            regards, tom lane