-
Notifications
You must be signed in to change notification settings - Fork 42
wrong type of text crashes the server #22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Might be good to submit this to [email protected] in case this is something that should be trapped in the engine, preventing a DB crash.
|
Unfortunately I don't think the backend can trap these things... Will look Dave Cramer On 16 June 2016 at 21:32, MattK [email protected] wrote:
|
I have a function that crashes my postgres 9.5 server. Here is the PL/R function:
When I run this, the whole server crashes, and all connections are dropped. Here is the main part of the error message in my postgresql logs:
Curiously, if I simply remove the return(svg) statement and instead do
return("foo")
, it works fine (but of course I don't get the output I want). So somehow the process of returning the svg string and coercing it to the postgresql text causes a hard crash. It is also odd to me that the regular old "plot" works just fine. Maybe that means this is a bug in svglite or ggplot2, but it would be nice if PL/R prevented server crashes as much as possible. Maybe it is something about the svg generated by ggplot2 that causes the problem.As a side note, I am new to PL/R but find it confusing how returning text often fails. For example, if I have two strings and concatenate them, no dice. That is, this doesn't work:
When running this I get nothing, whereas a simple
return("foo bar")
works just fine. If there is something I am doing wrong in either of these cases please advise. Thanks, and appreciate the efforts on PL/R, it is a very useful module.The text was updated successfully, but these errors were encountered: