From: | Greg Stark <stark(at)mit(dot)edu> |
---|---|
To: | David Beck <dbeck(at)starschema(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New hook after raw parsing, before analyze |
Date: | 2014-02-14 23:46:07 |
Message-ID: | CAM-w4HOtX9nSWMh7Xzc+j_=B-L-D9dcE6rdN+VcvoT9FYuiDNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 14, 2014 at 9:16 PM, David Beck <dbeck(at)starschema(dot)net> wrote:
> Another point I liked in mysql is the possibility to write info schema plugins: http://dev.mysql.com/doc/refman/5.1/en/writing-information-schema-plugins.html
> Like a virtual catalog. Is there anything similar in Postgres?
The documentation you linked to describes how to provide
information_schema plugins but not why you would want to do such a
thing. I'm not seeing why this would be useful. The information_schema
schema is described by the standard so creating new views in it isn't
needed very often and the schema for the existing views doesn't change
very often. I can see why a plugin might want to add rows to the views
but that doesn't seem to be what this feature is about.
--
greg
From | Date | Subject | |
---|---|---|---|
Next Message | Haribabu Kommi | 2014-02-14 23:47:28 | Re: Per table autovacuum vacuum cost limit behaviour strange |
Previous Message | Tom Lane | 2014-02-14 23:07:01 | Re: Ctrl+C from sh can shut down daemonized PostgreSQL cluster |