Re: plpgsql extension install nitpick

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql extension install nitpick
Date: 2011-07-03 16:48:30
Message-ID: 29637.1309711710@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
> On Sat, Jul 2, 2011 at 11:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Josh Kupershmidt <schmiddy(at)gmail(dot)com> writes:
>>> [ plpgsql's comment is now attached to the extension, not the PL itself ]
>>> ... And if you're wondering why I care
>>> about any of this, it's because I'd like to fix up psql's \dL command
>>> to display the comments attached to procedural languages, and I'd
>>> rather not have to special-case plpgsql.

>> Well, all four PLs supplied with core work the same way here, so a
>> special case targeted at only plpgsql would be quite wrong anyway.

> Not sure I follow you here... the COMMENT for plpgsql is in a
> different place than for 'c', 'internal', and 'sql', which is what I'm
> on about.

I was referring to plperl, plpython, pltcl. If we change this then all
four of those extensions should be changed the same way, The other
languages you mention are not extensions.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2011-07-03 18:04:13 Re: Deriving release notes from git commit messages
Previous Message Tom Lane 2011-07-03 16:46:15 Re: Deriving release notes from git commit messages