| From: | "Erik Rijkers" <er(at)xs4all(dot)nl> |
|---|---|
| To: | "Kevin Grittner" <kgrittn(at)ymail(dot)com> |
| Cc: | "Noah Misch" <noah(at)leadboat(dot)com>, "Kevin Grittner" <kgrittn(at)mail(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Marko Tiikkaja" <pgmail(at)joh(dot)to>, "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Materialized views WIP patch |
| Date: | 2013-02-19 22:09:13 |
| Message-ID: | 25965310c10b4d07bab2fd3c880135a3.squirrel@webmail.xs4all.nl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sat, February 16, 2013 02:01, Kevin Grittner wrote:
> matview-v4.patch.gz
Hi,
I was wondering if material views should not go into information_schema. I was thinking either
.views or .tables. Have you considered this?
I ask because as far as I can see querying for mv's has to go like this:
SELECT n.nspname, c.relname
FROM pg_catalog.pg_class c
LEFT JOIN pg_catalog.pg_namespace n ON n.oid = c.relnamespace
WHERE c.relkind IN ('m','')
and n.nspname = 'myschema'
which seems rather ugly.
Also, some documentation typos: please see attached.
Thanks,
Erik Rijkers
| Attachment | Content-Type | Size |
|---|---|---|
| matviewtypos.diff | application/octet-stream | 1.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-02-19 22:18:24 | Re: Materialized views WIP patch |
| Previous Message | Peter Eisentraut | 2013-02-19 16:01:36 | Re: Materialized views WIP patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-02-19 22:18:24 | Re: Materialized views WIP patch |
| Previous Message | Gurjeet Singh | 2013-02-19 21:50:45 | Patch to make pgindent work cleanly |