Re: query has no destination for result data

> On Mar 6, 2019, at 10:29 AM, Adrian Klaver wrote: > > On 3/6/19 8:19 AM, Rob Sargent wrote: >>> On Mar 6, 2019, at 7:41 AM, Adrian Klaver >> > wrote: >>> On 3/6/19 7:37 AM, Pavel Stehule wrote: or \sf+ functioname >>> >>> Cool, I learn

Re: query has no destination for result data

On 3/6/19 8:19 AM, Rob Sargent wrote: On Mar 6, 2019, at 7:41 AM, Adrian Klaver > wrote: On 3/6/19 7:37 AM, Pavel Stehule wrote: or \sf+ functioname Cool, I learned something new. Regards Pavel using \ef function 65 puts the cursor on the first lin

Re: query has no destination for result data

> On Mar 6, 2019, at 7:41 AM, Adrian Klaver wrote: > > On 3/6/19 7:37 AM, Pavel Stehule wrote: > >> or >> \sf+ functioname > > Cool, I learned something new. > >> Regards >> Pavel > > using \ef function 65 puts the cursor on the first line of the loop. So a debugging statement got in the

Re: query has no destination for result data

On 3/6/19 7:37 AM, Pavel Stehule wrote: or \sf+ functioname Cool, I learned something new. Regards Pavel -- Adrian Klaver adrian.kla...@aklaver.com

Re: query has no destination for result data

I believe language plpgsql is not considered part of the function body > so it is not included in the line count: > > https://www.postgresql.org/docs/10/plpgsql-structure.html > > When tracking a line number down I usually do: > > \ef some_function line_number > > which counts the line in the funct

Re: query has no destination for result data

On 3/6/19 7:12 AM, Rob Sargent wrote: On Mar 6, 2019, at 6:32 AM, Ron wrote: On 3/6/19 1:45 AM, Rob Sargent wrote: [snip] This construct had been working until recent changes but I cannot relate the message to any deformity in the current schema or code. Any pointers appreciated. What we

Re: query has no destination for result data

NOTICE:  2019-03-06 00:21:17.383835-07: added 3514 segments to imputed_pvalue_t ERROR:  query has no destination for result data HINT:  If you want to discard the results of a SELECT, use PERFORM instead. Below you have two other functions in play: optimal_pvalue_mono() ge

Re: query has no destination for result data

> On Mar 6, 2019, at 6:32 AM, Ron wrote: > > On 3/6/19 1:45 AM, Rob Sargent wrote: > [snip] >> This construct had been working until recent changes but I cannot relate the >> message to any deformity in the current schema or code. >> Any pointers appreciated. > > What were the recent changes

Re: query has no destination for result data

> On Mar 6, 2019, at 6:29 AM, Tom Lane wrote: > > Rob Sargent writes: >> One of my plpgsql functions is now throwing this error: > >> ERROR: query has no destination for result data >> HINT: If you want to discard the results of a SELECT, use PERFORM

Re: query has no destination for result data

On 3/6/19 1:45 AM, Rob Sargent wrote: [snip] This construct had been working until recent changes but I cannot relate the message to any deformity in the current schema or code. Any pointers appreciated. What were the recent changes? -- Angular momentum makes the world go 'round.

Re: query has no destination for result data

Rob Sargent writes: > One of my plpgsql functions is now throwing this error: > ERROR: query has no destination for result data > HINT: If you want to discard the results of a SELECT, use PERFORM instead. > CONTEXT: PL/pgSQL function optimal_pvalue_mono(text,text,integer,double

query has no destination for result data

oes not exist, skipping NOTICE: table "mrkidx" does not exist, skipping NOTICE: 2019-03-06 00:21:17.295142-07: working with 28607 markers NOTICE: 2019-03-06 00:21:17.383835-07: added 3514 segments to imputed_pvalue_t ERROR: query has no destination for result data HINT: If you want to disc