Thread: [BUGS] BUG #14703: documentation bug:
The following bug has been logged on the website: Bug reference: 14703 Logged by: Adam Sah Email address: asah@midgard.net PostgreSQL version: 9.6.3 Operating system: n/a Description: https://www.postgresql.org/docs/9.6/static/external-pl.html Fails to mention plv8 (aka Javascript), which is officially supported by Amazon RDS, i.e. unquestionably a mainstream option for a large number of pg admins, even if it's externally maintained. Here's the URL: https://github.com/plv8/plv8 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. thanks! adam -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
On Tue, Jun 13, 2017 at 9:51 AM, <asah@midgard.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
> 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.
I'm not sure how to interpret this followup...the original point being made is that we seem to have a documentation oversight and someone wanting to point out to non-technical people that PostgreSQL supports the pl/v8 language would not be able to point to this section of our documentation in order to do so.
The secondary reasoning is a bit circular since non-techies probably don't care too much about the fact that Amazon runs its own fork for RDS purposes - and at the same time those same people wouldn't take Amazon's support for pl/v8 to mean the underlying project supports it?
In any case I haven't seen any posts to general or hackers that would cause me to question the validity of adding it to our documentation listing.
David J.
Sorry to conflate RDS, I just meant it as evidence of plv8 being mainstream, NOT that pg docs should mention AWS in any way, which of course is inappropriate.
Sorry for the confusion!
Adam
(via cellphone, random spelling ahead)
On Jun 12, 2017 6:18 PM, "David G. Johnston" <david.g.johnston@gmail.com> wrote:
> 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.I'm not sure how to interpret this followup...the original point being made is that we seem to have a documentation oversight and someone wanting to point out to non-technical people that PostgreSQL supports the pl/v8 language would not be able to point to this section of our documentation in order to do so.The secondary reasoning is a bit circular since non-techies probably don't care too much about the fact that Amazon runs its own fork for RDS purposes - and at the same time those same people wouldn't take Amazon's support for pl/v8 to mean the underlying project supports it?In any case I haven't seen any posts to general or hackers that would cause me to question the validity of adding it to our documentation listing.David J.
On Tue, Jun 13, 2017 at 10:16 AM, David G. Johnston <david.g.johnston@gmail.com> wrote: > In any case I haven't seen any posts to general or hackers that would cause > me to question the validity of adding it to our documentation listing. I am not questioning that point. Adding a link to https://github.com/plv8/plv8 in the list of PLs in the docs makes perfect sense to me. -- Michael -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
On 6/12/17 21:35, Michael Paquier wrote: > On Tue, Jun 13, 2017 at 10:16 AM, David G. Johnston > <david.g.johnston@gmail.com> wrote: >> In any case I haven't seen any posts to general or hackers that would cause >> me to question the validity of adding it to our documentation listing. > > I am not questioning that point. Adding a link to > https://github.com/plv8/plv8 in the list of PLs in the docs makes > perfect sense to me. done -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs