Michael Vitale

@Andersson007, adding this info to my playbook did the trick. But if I have a role that invokes this task, is there something I can do when my playbook consists...

Perhaps we can update the example in the documentation for postgresql_ping to add the check for **is_available** return value: ``` # In the example below you need to generate certificates...

@klando copied documentation related to this discussion that basically said that the purpose of the PG ping is to evaluate the status of a PG cluster, not a specific database...

I changed the title of this issue to something more relevant to the evolving focus here: **Using is_available return variable to determine if PG Ping is success or failure**

@klando, gotcha, will edit my comment to reflect that.

OK, then, I reckon @klando is saying take out the database name option from the ping call just to see if we can connect or not. I'm for that. We...

I'd like to know the answer to this too.

Fixed for views. Keeping this open for other dependency issues that may come up.

First of all, the temp file is generated on the DB server, not locally on your client machine. It should still be there since the same file is used over...

Can you provide the table DDL? or perhaps create a small sample table that can demonstrate this problem and post here.