Re: Inconsistent compilation error - Mailing list pgsql-general

From Melvin Davidson
Subject Re: Inconsistent compilation error
Date
Msg-id CANu8FizKT7WsO1xDWkcVhCmLQ1cOR1P6zEPwdXtgmg7HfO=pWA@mail.gmail.com
Whole thread Raw
In response to Re: Inconsistent compilation error  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general


On Thu, Apr 19, 2018 at 8:13 AM, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Wednesday, April 18, 2018, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
Hmm, wonder if there is an oops in the below:

http://www.pygresql.org/contents/changelog.html

Version 5.0 (2016-03-20)
Changes in the DB-API 2 module (pgdb):
"SQL commands are always handled as if they include parameters, i.e. literal percent signs must always be doubled. This consistent behavior is necessary for using pgdb with wrappers like SQLAlchemy."

I'd hope not, as far as the driver is concerned the percent signs are text content.  It's plpgsql that is interpreting them directly in the server.

David J.

Hmmm, looking at the code you provided us, it is obviously not what is actually in production. So if you copy the actual function from the system that works
and use that to frop and rebuild the function on the system that fails, does that resolve the problem?
I suspect there is an error in the failing system that you have overlooked.

--
Melvin Davidson
Maj. Database & Exploration Specialist

Universe Exploration Command – UXC

Employment by invitation only!

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Problem with trigger makes Detail record be invalid
Next
From: Ron
Date:
Subject: A couple of pg_dump questions