From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu> |
Cc: | David Beck <dbeck(at)starschema(dot)net>, "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:49:01 |
Message-ID: | 23879.1392421741@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greg Stark <stark(at)mit(dot)edu> writes:
> 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.
IIRC, mysql has a liberal view about what they can do to the
information_schema, so for them this isn't as insane as it sounds to us.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2014-02-14 23:57:38 | Re: New hook after raw parsing, before analyze |
Previous Message | Haribabu Kommi | 2014-02-14 23:47:28 | Re: Per table autovacuum vacuum cost limit behaviour strange |