Parse the search_path from the database URL or extract it from the

[vivere-dally]

RIVER_SCHEMA env var and pass it to the River client's Config. Should allow usage for users that do not have the river tables in the postgres public schema.

My use case: I have the river tables under the jobs schema. I tried any way I could find to specify the schema.

[brandur]

@vivere-dally Thanks! Just to be clear, are you saying that the use of search_path isn't working? I can't remember if we tested that or not, but it'd be good just to confirm that that we are diagnosing the right problem here — would you mind posting the error that you're getting?

Also, just in case we end up merging this, could you correct the PR title/description for cleanliness? it kind of looks like they both blended together from one piece of content.