postgres

mirror of https://github.com/postgres/postgres.git synced 2025-04-24 10:47:04 +03:00

History

Tom Lane e7941a9766 Replace over-optimistic Assert in partitioning code with a runtime test.

get_partition_parent felt that it could simply Assert that systable_getnext
found a tuple.  This is unlike any other caller of that function, and it's
unsafe 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't
expecting the DB to fall over quite that violently.  The behavior in a
non-assert-enabled build wouldn't be very nice, either.)  Fix it to do what
other callers do, namely an actual runtime-test-and-elog.

Also, standardize the wording of elog messages that are complaining about
unexpected failure of systable_getnext.  90% of them say "could not find
tuple for <object>", so make the remainder do likewise.  Many of the
holdouts were using the phrasing "cache lookup failed", which is outright
misleading since no catcache search is involved.

2017-06-04 16:20:03 -04:00

expected

Fix contrib/sepgsql regression tests for partition NOT NULL change.

2017-05-21 11:46:04 -04:00

sql

Fix whitespace

2017-04-10 11:18:15 -04:00

.gitignore

Minor sepgsql regression test fixes.

2011-02-02 23:46:51 -05:00

database.c

Replace over-optimistic Assert in partitioning code with a runtime test.