You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Replace over-optimistic Assert in partitioning code with a runtime test.
get_partition_parent felt that it could simply Assert that systable_getnextfound a tuple. This is unlike any other caller of that function, and it'sunsafe IMO --- in fact, the reason I noticed it was that the Assert failed.(OK, I was working with known-inconsistent catalog contents, but I wasn'texpecting the DB to fall over quite that violently. The behavior in anon-assert-enabled build wouldn't be very nice, either.) Fix it to do whatother callers do, namely an actual runtime-test-and-elog.Also, standardize the wording of elog messages that are complaining aboutunexpected failure of systable_getnext. 90% of them say "could not findtuple for <object>", so make the remainder do likewise. Many of theholdouts were using the phrasing "cache lookup failed", which is outrightmisleading since no catcache search is involved.