Re: BUG #13960: plpython fails with certain function names

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim(dot)Nasby(at)BlueTreble(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13960: plpython fails with certain function names
Date: 2016-02-15 00:49:59
Message-ID: 3868.1455497399@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Jim(dot)Nasby(at)BlueTreble(dot)com writes:
> If a Postgres function contains characters that are illegal for python
> identifiers, compilation fails. Error message is not very helpful either:

Hm, how much do we really care? The example seems kinda artificial.

> One possibility is to simply strip out invalid characters[1].

No, because then you would get collisions, ie function names that look
different to PG would look the same to python. Bad news.

(Actually, don't we have that issue anyway because of schemas? I wonder
why we are exposing the PG name of the function to python at all.)

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jim Nasby 2016-02-15 00:56:33 Re: BUG #13960: plpython fails with certain function names
Previous Message Michael Paquier 2016-02-15 00:24:32 Re: Standbys using commas in application_name cannot become sync nodes