fix, adjust OID query without range support to include required fields.

This is a follow-up fix to f7a6b115fea9f675190a79b701c7034214678f19 and
06082f66d541e581110406bbac3bc395bace3f86
Clarify 'database does not exist' message and implementation.

* Clarify what the situation is and what to do.
* Advise loading schema using `rake db:setup` instead of migrating.
* Use a rescue in the initializer rather than extending the error
  message in-place.
* Preserve the original backtrace of other errors by using `raise`
  rather than raising again with `raise error`.

References 0ec45cd15d0a2f5aebc75e23d841b6c12f3ba763
only ask if `t` is empty once.
do not create memo objects since we'll just throw them away
combine move_regexp and move_string so we only loop over states once
push move_string in to `move`
Merge branch 'rmc'

* rmc:
  push move_string in to `move`
  combine move_regexp and move_string so we only loop over states once
  do not create memo objects since we'll just throw them away
  only ask if `t` is empty once.
Changed 'so' to 'see'
Allow postgresql enum_test to be run in random order.

Creating and dropping similar tables within the same connection causes postgresql to look up old values in the cache of tables which have already been dropped.
Merge pull request #14560 from abwinkler999/typo-in-RELEASING_RAILS

Changed 'so' to 'see'
Merge pull request #14550 from tgxworld/fix_failing_enum_test_random_order

Allow postgresql enum_test to be run in random order.
cleanup, `reset_pg_session` in range_test.rb

Also do not use transactional fixtures. We drop the type and the
table after every run, so there is nothing for the transaction to clean up.
PostgreSQL, Support for materialized views. [Dave Lee & Yves Senn]

Expand the query used in #table_exists? to include materialized views in the
kinds of relations it searches.
A new trie based router

This commit completely replaces Journey as the router in Rails. The reasoning
being it is a lot less code and also IMO conceptually easier to understand than
NFAs and GTGs. It also performs significantly better than Journey. I wrote a
simple benchmark containing 336 routes that each respective router was required
to match 1000 times, with the averaged time of 5 runs taken as the result.
Journey completed this in 39.97 seconds and this router in 32.61 seconds.

The simple case is a path is split on forward slashes and each segment is a
child of the preceding segment with the route object stored at the terminal
leaf node. The result is tree-like structure with O(log n) runtime
characteristics as the route table grows. In practice with optional segments,
more than one node on the path may point to the same route object. This is so
/:controller matches as well as /:controller/:action does given the path
/:controller(:/action(/:id))(.:format)

The code is straightforward to understand if you seek further details.