Error after renaming Postgres enum value when that enum type is in use by a table

readysettech / readyset

Readyset is a MySQL and Postgres wire-compatible caching layer that sits in front of existing databases to speed up queries and horizontally scale read throughput. Under the hood, ReadySet caches the results of cached select statements and incrementally updates these results over time as the underlying data changes.

Other

4.56k stars 126 forks source link

Found this via the vertical DDL test. I think I was able to repro via a fallback test, though the error looks a little bit different, and it doesn’t seem to require writing a row to the table even though the vertical DDL tests included that in their minimal repro.

Steps are simply:

Create an enum type
Create a table that uses that enum type
Rename one of the enum type’s values (via ALTER TYPE ... RENAME VALUE ... TO ...)
CREATE CACHE ALWAYS a simple SELECT query against the table

The fallback test (which I’ll submit as an ignored test in a CL shortly) gives me an unknown: Failed to manipulate view at NodeIndex(4): view destroyed error, and subsequent retry queries give the error unknown: Could not find view q_833e4ae281569fd9 until the eventually! call times out and fails the test.

_{From SyncLinear.com | REA-2472}

readysettech / readyset

Error after renaming Postgres enum value when that enum type is in use by a table #108