Re: [SQL] primary key view failure

rob caSSon <rob(at)styro(dot)lib(dot)muohio(dot)edu> writes:
> should have sent this along in the first place....
> using latest unstable debian package...6.5.1-4

OK, then it evidently is a bug or porting problem. Hard to say
what though; we need more evidence.

Is there any difference in the plans you get from "explain" of the
direct query and the view query? I get this either way:

Hash Join (cost=83.94 rows=19044 width=94)
-> Nested Loop (cost=53.62 rows=552 width=58)
-> Seq Scan on pg_index (cost=2.19 rows=1 width=20)
-> Seq Scan on pg_attribute (cost=51.43 rows=1104 width=38)
-> Hash (cost=6.55 rows=138 width=36)
-> Seq Scan on pg_class (cost=6.55 rows=138 width=36)

regards, tom lane