From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Phil Sorber <phil(at)omniti(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Prepared Statement Name Truncation |
Date: | 2012-11-18 07:33:02 |
Message-ID: | 23706.1353223982@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
Phil Sorber <phil(at)omniti(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jacek Domagalski | 2012-11-18 13:20:55 | Re: BUG #7667: Segmentation fault |
Previous Message | Tom Lane | 2012-11-18 07:24:03 | Re: [GENERAL] Prepared Statement Name Truncation |
From | Date | Subject | |
---|---|---|---|
Next Message | Abel Abraham Camarillo Ojeda | 2012-11-18 07:48:39 | Re: Difference between varchar and text? |
Previous Message | Tom Lane | 2012-11-18 07:29:56 | Re: Difference between varchar and text? |