From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | asah(at)midgard(dot)net |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14703: documentation bug: |
Date: | 2017-06-13 01:04:53 |
Message-ID: | CAB7nPqROhuQn71G4NEoqdMGDRRT+Dcxv7hMvBN4C+FAF1ACKFQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Jun 13, 2017 at 9:51 AM, <asah(at)midgard(dot)net> wrote:
> Here's the URL:
> https://github.com/plv8/plv8
Perhaps it makes sense to add it, it is popular and has been around
for some time now.
> Amazon RDS docs mentioning plv8 support:
> http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html
>
> This is important for business approvers signing off on using Postgres, who
> expect to see Javascript support, and need more 'social proof' than Amazon
> AWS documentation.
But there is no way to be sure if the version shipped with RDS has
been modified or not, or if there are restrictions applying to it so
it is hard to believe that the *actual* upstream code is supported and
if that's what is being used or not. The core Postgres engine has for
example a set of custom patches applied on top of it.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-06-13 01:16:53 | Re: BUG #14703: documentation bug: |
Previous Message | asah | 2017-06-13 00:51:32 | BUG #14703: documentation bug: |