BUG #6634: pg_dump dumps cast after objects depending on it

The following bug has been logged on the website:

Bug reference: 6634
Logged by: András Váczi
Email address: avandras(at)gmail(dot)com
PostgreSQL version: 9.1.3
Operating system: Ubuntu 10.04.4 LTS
Description:

A cast, which transforms a composite type to timestamp without time zone, is
included in the regular backups of a database.
There are several views utilizing this cast, but these are always listed
before the cast, therefore pg_restore or psql will issue an error instead of
creating the view.
This causes that the DB cannot be successfully restored, only with the help
of an additional patch file, which must be maintained by hand.

avandras(at)gmail(dot)com writes:
> A cast, which transforms a composite type to timestamp without time zone, is
> included in the regular backups of a database.
> There are several views utilizing this cast, but these are always listed
> before the cast, therefore pg_restore or psql will issue an error instead of
> creating the view.

Please provide a concrete example.

regards, tom lane

=?ISO-8859-1?B?QW5kcuFzIFbhY3pp?= <avandras(at)gmail(dot)com> writes:
> Object list as pg_restore outputs (see error log below):

That is not tremendously helpful. pg_dump should generally dump casts
before views, and you have not provided any information that would tell
why it's not doing so in this case. We need to see a complete *self
contained* test case, such as a SQL script that creates a set of objects
that don't dump correctly.

regards, tom lane