Re: field error on refreshed materialized view

From: Michael Nolan <htfoot(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: field error on refreshed materialized view
Date: 2024-01-27 20:28:43
Message-ID: CAOzAquK_y4L3pqhU5iq=DKEEg9=eCSu4YJ+e-i0VAtb1HNfNuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2024-01-27 21:27:09 Re: field error on refreshed materialized view
Previous Message Junwang Zhao 2024-01-27 05:55:23 Re: Emitting JSON to file using COPY TO