Please add more information to your issue. Without test instructions and/or any description we will close this issue within 4 weeks. Thanks.
This is an automated message from the J!Tracker Application.

The bug that this path fixes, and some thoughts about the solution are described at #7834

I will summurize here anyway. Using the latest version of Joomla, on a PostgreSQL database and trying to edit a template you will obtain the error shown below:

I haven't tested on PostgreSQL, but on MySQL it obviously works fine.
Inspecting $published while opening a template style also shows me that it is empty. Thus the code in question isn't fired at all.
Looking at your screenshot, it looks like you are using at least some 3rd party plugins or even a template with a framework. Which makes me believe the issue is caused from there.
That $published variable should contain an array of integers with the values of the states to be filtered. Passing true or false would be wrong values.

If you want to sanitise it, you may instead use $published = JArrayHelper::toInteger($published) which will cast the values to integer and remove any non-integer values. Making the code much easier to read.

without this pr on postgresql no problem on edit and save a "core template" without 3dp
so unable to reproduce

@vtamara Can you provide details with which template you had this issue? Or what the exact steps are to reproduce the issue?

I'm using T3 Framework with template Purity III --that announce to work on PostgreSQL

Using $published = JArrayHelper::toInteger($published) instead of the filter I proposed gives the following error:

Ah, that may be because you end up with all invalid entries in the array and thus implode on an empty array.

We could add a check to see if the array contains anything after it's passed through the JArrayhelper. But honestly I think it's a bug in the T3 framework which should be fixed by them, they seem to pass "true" instead of "1".
We can (and should) sanitise the input on our part, but fixing the issue is their job.

Thank you. Confirmed it is a T3 issue I'm proposing solution there and closing here.

t3framework/t3#423