Re: field error on refreshed materialized view - Mailing list pgsql-general

From Michael Nolan
Subject Re: field error on refreshed materialized view
Date
Msg-id CAOzAquK_y4L3pqhU5iq=DKEEg9=eCSu4YJ+e-i0VAtb1HNfNuw@mail.gmail.com
Whole thread Raw
In response to Re: field error on refreshed materialized view  (Michael Nolan <htfoot@gmail.com>)
Responses Re: field error on refreshed materialized view
List pgsql-general
Followup:  The problem turned out to be a field in the mysql server
that was not size-limited to 255 characters and had several rows with
as many as 299 characters in them.  Apparently when using an FDW and
materialized view in postgresql 10.4, field size limits aren't
checked, because a query on the matview in the 10.4 system finds those
records with more than 255 characters in that field.

So, not a character encoding issue at all.
--
Mike Nolan



pgsql-general by date:

Previous
From: pf@pfortin.com
Date:
Subject: Re: permission denied on socket
Next
From: Tom Lane
Date:
Subject: Re: field error on refreshed materialized view