I see that mysql 8.0 is supported and I guess from the older days, pg 9.6 will be supported to (I tried 9.6, it worked).
I also tried pg 12 and yet it seems to work too. My site is fairly limited, it is only used for translations, so views/bulk and potx, some l10n stuff and that's about it. No CCK even.
What are your expectations with d6lts and pg 12?
Also, maybe a different topic, if i find any issue and patch those, would you be interested in merging those?
I understand, nobody can judge anything about the contribs, so the question can be handled differently for
a) core
b) contribs (which are already part of d6lts like views/views bulk)
c) yet unsupported contribs
Background: we picked 12 because of the changesin cluster setups and performance of pg12. We cannot really downgrade since tools like crunchydata only support pg12+ nowadays. (most of them).
Just for anybody reading this, we are running on pg14 for more then a year now. We have a very limited scope for the usage of this one d6 instance and for this (translations) it works just fine.
I see that mysql 8.0 is supported and I guess from the older days, pg 9.6 will be supported to (I tried 9.6, it worked).
I also tried pg 12 and yet it seems to work too. My site is fairly limited, it is only used for translations, so views/bulk and potx, some l10n stuff and that's about it. No CCK even.
What are your expectations with d6lts and pg 12? Also, maybe a different topic, if i find any issue and patch those, would you be interested in merging those?
I understand, nobody can judge anything about the contribs, so the question can be handled differently for a) core b) contribs (which are already part of d6lts like views/views bulk) c) yet unsupported contribs
Background: we picked 12 because of the changesin cluster setups and performance of pg12. We cannot really downgrade since tools like
crunchydata
only support pg12+ nowadays. (most of them).Let me know about your thoughts!