| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13960: plpython fails with certain function names |
| Date: | 2016-02-17 01:23:38 |
| Message-ID: | 56C3CB9A.4030009@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2/14/16 7:09 PM, Tom Lane wrote:
> Yeah, that's what I was thinking about. But yes, if we append the OID
> anyway then we might as well just strip all non-alphanumeric chars
> from the name. Safe and you still get some debuggability.
Attached. I opted not to modify the name in-place. If it's safe to
modify in place, might want to just replace invalid characters with '_'
instead of making a copy.
--
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
| Attachment | Content-Type | Size |
|---|---|---|
| plpython_name.patch | text/plain | 3.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-02-17 01:49:38 | Re: BUG #13960: plpython fails with certain function names |
| Previous Message | Tatsuo Ishii | 2016-02-17 00:25:51 | Re: Encoding problems with "COMMENT ON DATABASE .." causing pg_restore (and pg_upgrade) to fail |