I wrote:
> 168; 1259 41968 TABLE public t1 postgres
> ; depends on: 5
> 1921; 2606 41975 CONSTRAINT public t1_pkey postgres
> ; depends on: 168 168
> 169; 1259 41976 VIEW public v1 postgres
> ; depends on: 1919 5
> 1922; 0 41968 TABLE DATA public t1 postgres
> ; depends on: 168
BTW, there's another pretty unpleasant thing going on here, which is
that the t1_pkey constraint is getting hoisted up to before t1's table
data because it is a dependency of v1. That means the index will be
created before the data is loaded, which is not what we want.
Parallel pg_restore actually has a hack that should work around that,
namely repoint_table_dependencies(). That doesn't help for plain serial
restores though. I'm thinking we really ought to bite the bullet and do
something comparable to repoint_table_dependencies() at an appropriate
point in pg_dump, so that the dependencies are sane to begin with.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
