From: Tom Lane <tgl@sss.pgh.pa.us>
To: rob caSSon <rob@styro.lib.muohio.edu>
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] primary key view failure
Date: Thu, 05 Aug 1999 11:47:02 -0400
Message-ID: <4647.933868022@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.3.96.990805112045.13176A-100000@styro.lib.muohio.edu>
rob caSSon <rob@styro.lib.muohio.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, rob@styro.lib.muohio.edu
Subject: Re: [SQL] primary key view failure
In-Reply-To: <4647.933868022@sss.pgh.pa.us>
References: <Pine.LNX.3.96.990805112045.13176A-100000@styro.lib.muohio.edu> <4647.933868022@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox