1
0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
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
..
2017-05-17 16:31:56 -04:00
2017-05-17 16:31:56 -04:00
2017-05-17 16:31:56 -04:00
2017-02-06 11:33:58 +02:00
2017-05-17 16:31:56 -04:00
2017-05-17 19:01:23 -04:00
2017-03-14 12:58:39 -04:00
2017-05-17 16:31:56 -04:00
2017-05-17 16:31:56 -04:00
2017-03-30 14:18:53 -04:00
2017-03-30 14:18:53 -04:00
2017-05-17 16:31:56 -04:00
2017-05-17 16:31:56 -04:00
2017-05-17 16:31:56 -04:00
2017-05-17 16:31:56 -04:00
2017-03-14 12:58:39 -04:00
2017-02-06 11:33:58 +02:00
2017-01-03 13:48:53 -05:00
2017-03-09 16:33:02 -08:00

The PostgreSQL contrib tree
---------------------------

This subtree contains porting tools, analysis utilities, and plug-in
features that are not part of the core PostgreSQL system, mainly
because they address a limited audience or are too experimental to be
part of the main source tree.  This does not preclude their
usefulness.

User documentation for each module appears in the main SGML
documentation.

When building from the source distribution, these modules are not
built automatically, unless you build the "world" target.  You can
also build and install them all by running "make all" and "make
install" in this directory; or to build and install just one selected
module, do the same in that module's subdirectory.

Some directories supply new user-defined functions, operators, or
types.  To make use of one of these modules, after you have installed
the code you need to register the new SQL objects in the database
system by executing a CREATE EXTENSION command.  In a fresh database,
you can simply do

    CREATE EXTENSION module_name;

See the PostgreSQL documentation for more information about this
procedure.