Prev: [PATCH] Largeobject Access Controls (r2460)
Next: Sought after architectures for the PostgreSQL buildfarm?
From: Josh Berkus on 7 Dec 2009 13:39
All,

What it's sounding like is that we ought to have a plug-in (both for
postmaster and for psql) which allows the calling of an external library
to parse explain output. Then people could covert XML/JSON into
whatever they wanted.

--Josh Berkus


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Andrew Dunstan on 7 Dec 2009 14:07


Josh Berkus wrote:
> All,
>
> What it's sounding like is that we ought to have a plug-in (both for
> postmaster and for psql) which allows the calling of an external library
> to parse explain output. Then people could covert XML/JSON into
> whatever they wanted.
>
>
>

Not everything is sanely convertible into some sort of plugin. A plugin
mechanism for this would be FAR more trouble that it is worth, IMNSHO.

We are massively over-egging this pudding (as a culinary blogger you
should appreciate this analogy).

cheers

andrew

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Greg Smith on 7 Dec 2009 14:26
Josh Berkus wrote:
> What it's sounding like is that we ought to have a plug-in (both for
> postmaster and for psql) which allows the calling of an external library
> to parse explain output. Then people could covert XML/JSON into
> whatever they wanted.
>
It would be kinder to just reject the YAML patch than to make it wait
for this.

--
Greg Smith 2ndQuadrant Baltimore, MD
PostgreSQL Training, Services and Support
greg(a)2ndQuadrant.com www.2ndQuadrant.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Josh Berkus on 7 Dec 2009 16:53

> Not everything is sanely convertible into some sort of plugin. A plugin
> mechanism for this would be FAR more trouble that it is worth, IMNSHO.
>
> We are massively over-egging this pudding (as a culinary blogger you
> should appreciate this analogy).

OK, then let's just accept it. It's small, has a maintainer, is useful
to some people, and doesn't create any wierd complications. I think,
given the knowledge that YAML is now a subdialect of JSON it could
potentially be made smaller, but I can't say how at the moment.

--Josh Berkus

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Andrew Dunstan on 7 Dec 2009 19:07


Josh Berkus wrote:
>> Not everything is sanely convertible into some sort of plugin. A plugin
>> mechanism for this would be FAR more trouble that it is worth, IMNSHO.
>>
>> We are massively over-egging this pudding (as a culinary blogger you
>> should appreciate this analogy).
>>
>
> OK, then let's just accept it. It's small, has a maintainer, is useful
> to some people, and doesn't create any wierd complications. I think,
> given the knowledge that YAML is now a subdialect of JSON it could
> potentially be made smaller, but I can't say how at the moment.
>
>
>

Actually, it's the other way, JSON is a subset of YAML.

I was in fact prepared to commit this patch, despite some significant
misgivings about its wisdom, mainly because it does have such a low
impact. But then other people raised objections. I'm not sure how strong
those objections are, though.

I must say that while the YAML output might look a bit nicer than the
JSON output, the difference strikes me as mostly marginal. But I guess
it's like beauty and obscenity, something in the eye of the beholder. De
gustibus non est disputandum.

cheers

andrew




--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 |  Next  |  Last
Pages: 1 2 3
Prev: [PATCH] Largeobject Access Controls (r2460)
Next: Sought after architectures for the PostgreSQL buildfarm?