Re: BUG #13960: plpython fails with certain function names
| От | Jim Nasby |
|---|---|
| Тема | Re: BUG #13960: plpython fails with certain function names |
| Дата | |
| Msg-id | 56C3D292.9060507@BlueTreble.com обсуждение исходный текст |
| Ответ на | Re: BUG #13960: plpython fails with certain function names (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: BUG #13960: plpython fails with certain function names
|
| Список | pgsql-bugs |
On 2/16/16 7:49 PM, Tom Lane wrote: > I like the idea of replacing invalid characters with '_'. It's definitely > not safe to scribble on the pg_proc tuple, but we could get the same > result with a few wasted cycles by rescanning the procName string after > building it, as per attached. Heck, I didn't even think about that. Yeah, it's going to scan another 20 bytes or so, but this certainly isn't performance critical. BTW, I didn't bother checking this with python 3.5, but I can't fathom how that would matter here. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com
В списке pgsql-bugs по дате отправления: