Crashes during initial setup with PG 16 dbs

[Lysholm]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem
• ... it's definitely a Firefly III issue, not me

Description

Since PG 15 the 'public' schema is without grants on them by default resulting in the initial setup failing.

This can be worked around by having a super user grant those necessary privileges, but in security conscious setups (clod provided or default percona/pg-db deployment ie.) that's not viable.

Changing the default schema in firefly would be ideal but I guess that might be a bit of an unkind upgrade. Documenting the limitation and how to use the env variable added with #5503 would be nice. I can do a PR if you give me a hint where you'd prefer it documented.

Debug information

Don't get to this point service never readies up.

Expected behaviour

No response

Steps to reproduce

1. Install PG 16
2. Try starting latest firefly

Additional info

No response

[JC5]

I have no idea what you're talking about, sorry.

[Lysholm]

@JC5 PGSQL_SCHEMA is set to 'public' by default. Since PG 15 only a user with "SUPERUSER" role can write there, unless specifically granted access on that schema.

[JC5]

Ah, postgresql, got it!

Let me think about it. Perhaps a note in .env.example is enough.

[JC5]

If you could extend this comment, that would be perfect.

https://github.com/firefly-iii/firefly-iii/blob/main/.env.example#L114

[github-actions]

Hi there!

This is an automatic reply. Share and enjoy

This issue has been marked as an enhancement. The requested enhancement to an existing feature will become a part of Firefly III or the data importer in due course.

If you come across this issue, please be aware there is NO need to reply with "+1" or "me too" or "I need this too" or whatever. Such comments are not helpful, and do not influence the roadmap. Your comment may be 💀 deleted. You can subscribe to this issue to get updates.

Thank you for your contributions.