Re: Inconsistent compilation error - Mailing list pgsql-general

From Melvin Davidson
Subject Re: Inconsistent compilation error
Date
Msg-id CANu8Fizyk-Q_sHdy6F9vFZk-hcednx-paP_woj=WgKjkuDbXOg@mail.gmail.com
Whole thread Raw
In response to Re: Inconsistent compilation error  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: Inconsistent compilation error  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-general
> I'm unsure why you're considering
>'blah_history.original_id' not to be an argument here.

On Wed, Apr 18, 2018 at 9:50 PM, David Rowley <david.rowley@2ndquadrant.com> wrote:
On 19 April 2018 at 13:28, Melvin Davidson <melvin6925@gmail.com> wrote:
> It is not fine. You have specifed TWO percent signs (%) which requires TWO
> argumenrts,
> but you have only provided ONE -> r.

I'm confused about this statement.

Did you perhaps overlook the fact that there are in fact two
arguments? I'm unsure why you're considering
'blah_history.original_id' not to be an argument here.


--
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

There are two possibilities here.
1`. The compiler might be expecting a variable and not accepting a text literal.
Normally, literals are inside the first quotes. IE: raise notice ' blah_history.original_id' %', r;
OR
2. since this is in a loop, r might be NULL




--
Melvin Davidson
Maj. Database & Exploration Specialist

Universe Exploration Command – UXC

Employment by invitation only!

pgsql-general by date:

Previous
From: David Rowley
Date:
Subject: Re: Inconsistent compilation error
Next
From: Tom Lane
Date:
Subject: Re: Inconsistent compilation error