Michael Nolan writes:
> 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'
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 t
On Thu, Jan 25, 2024 at 3:38 PM Tom Lane wrote:
>
> Michael Nolan writes:
> > 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
Michael Nolan writes:
> 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)
> Both materialized view tables appear to be iden
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
