Re: field error on refreshed materialized view

On 1/25/24 1:29 PM, Michael Nolan wrote:
> I'm in the process of updating a server from postgresql 10.4 on Centos
> 7 to 16.1 on AlmaLInux 9, and am reminded of the old line about when
> you're up to your necks in alligators, it is difficult to remember
> that your goal was to drain the swamp.
>
> We have several materialized views that are refreshed from an external
> mysql/mariadb server.

Define "... refreshed from an external mysql/mariadb server"?

>
> On the 10.4 server this materialized view works, but on the 16.1
> server it fails:
>
> uscf=# refresh materialized view uscf_vip;
> refresh materialized view uscf_vip;
> ERROR: value too long for type character varying(255)

Is there more to the error, that shows the actual value?

Or have you looked in server log to see if there is more information?

>
> Both materialized view tables appear to be identical. (We did a
> restore from a recent database dump to populate the new server.)
>
> I don't see anything in the log files to help me determine which field
> or row is causing the error. As far as I can tell, encoding is the
> same on both versions, but there could be issues in how the mysql
> server is coding non-ASCII characters.
>
> Is this something that has to be tracked down on the mysql/mariadb
> server or is there anything I can do to help narrow down the problem
> on my 16.1 server?
> --
> Mike Nolan
> htfoot(at)gmail(dot)com
>
>