Re: The missing pg_get_*def functions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Joel Jacobson <joel(at)trustly(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: The missing pg_get_*def functions
Date: 2013-04-30 14:49:56
Message-ID: 3741.1367333396@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> If all you want is SQL language functions, there is nothing to stop you
> from writing them and publishing them today as an extension.

It's worth noting also that we actually *have* infrastructure for
updating extensions without initdb; unlike the initial contents of
pg_proc. So this approach is more attractive than it might seem
on its face, assuming you are going to do this as SQL functions.
(I share the doubts expressed elsewhere as to how feasible that
actually is.)

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-04-30 14:51:23 Re: Substituting Checksum Algorithm (was: Enabling Checksums)
Previous Message Kevin Grittner 2013-04-30 14:40:19 Re: Remaining beta blockers