From: | Dave Page <dave(dot)page(at)enterprisedb(dot)com> |
---|---|
To: | Neel Patel <neel(dot)patel(at)enterprisedb(dot)com> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Materialized View Patch File |
Date: | 2013-05-31 12:29:48 |
Message-ID: | CA+OCxoxZWzEvJqY8+HS2vzjKSBHiKphQbPHVgXBENKGPvZ9Xfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
On Wed, May 29, 2013 at 10:40 AM, Neel Patel
<neel(dot)patel(at)enterprisedb(dot)com> wrote:
> Hi Dave,
>
> Please find the updated patch after fixing some of the issues and comments
> given by Ashesh.
I haven't looked at the code, but judging by the error I got when
first clicking on a view on a PG 9.2 server, you forgot to make this
code version-dependent:
2013-05-31 13:25:57 QUERY : Scalar query (localhost:5432): SELECT
count(*) FROM pg_matviews WHERE matviewname = 'pem.avail_servers' AND
schemaname = 'pem'
2013-05-31 13:25:57 ERROR : ERROR: relation "pg_matviews" does not exist
LINE 1: SELECT count(*) FROM pg_matviews WHERE matviewname = 'pem.av...
^
It then goes on to give the view definition as:
-- MATERIALIZED View: pem.avail_servers
-- DROP MATERIALIZED VIEW pem.avail_servers;
CREATE MATERIALIZED VIEW pem.avail_servers AS
SELECT s.id, s.description, s.server, s.port, s.database, s.ssl, s.serviceid,
...
...
(as a side note, the first line for a real mat view should be: "--
Materialized View: pem.avail_servers")
--
Dave Page
Chief Architect, Tools & Installers
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
From | Date | Subject | |
---|---|---|---|
Next Message | Neel Patel | 2013-06-03 06:56:37 | Re: Materialized View Patch File |
Previous Message | Neel Patel | 2013-05-29 09:40:18 | Re: Materialized View Patch File |