Re: RDS and postgres extension approval

On 10/21/21 21:42, Wells Oliver wrote:
> Hi-- maybe more an RDS question, but does anyone know how
> extensions go about being approved for use in PG on RDS? For example,
> we'd like to make use of plpython3u but you get the old "Extension
> "plpython3u" is not supported by Amazon RDS" error..
>
> --
> Wells Oliver
> wells(dot)oliver(at)gmail(dot)com <mailto:wellsoliver(at)gmail(dot)com>

You should try PLPerl. That extension is supported by RDS:

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_PostgreSQL.html#PostgreSQL.Concepts.General.FeatureSupport.Extensions.12x

Your code will look prettier, thanks to perltidy. You will also get the
whole of CPAN in your toolkit. Above all, you will not have to use
COBOL-like tabulation. Whatever you can do in Python, you can also do in
Perl. And, as always, use strict.

#!/usr/bin/perl -w # camel code use strict; $_='ev al("seek\040D ATA,0,
0;");foreach(1..3) {<DATA>;}my @camel1hump;my$camel; my$Camel ;while(
<DATA>){$_=sprintf("%-6 9s",$_);my(at)dromedary 1=split(//);if(defined($
_=<DATA>)){(at)camel1hum p=split(//);}while(@dromeda ry1){my$camel1hump=0
;my$CAMEL=3;if(defined($_=shif t(@dromedary1
))&&/\S/){$camel1hump+=1<<$CAMEL;} $CAMEL--;if(d
efined($_=shift(@dromedary1))&&/\S/){ $camel1hump+=1
<<$CAMEL;}$CAMEL--;if(defined($_=shift(
@camel1hump))&&/\S/){$camel1hump+=1<<$CAMEL;}$CAMEL--;if(
defined($_=shift(@camel1hump))&&/\S/){$camel1hump+=1<<$CAME
L;;}$camel.=(split(//,"\040..m`{/J\047\134}L^7FX"))[$camel1h
ump];}$camel.="\n";}(at)camel1hump=split(/\n/,$camel);foreach(@
camel1hump){chomp;$Camel=$_;y/LJF7\173\175`\047/\061\062\063\
064\065\066\067\070/;y/12345678/JL7F\175\173\047`/;$_=reverse;
print"$_\040$Camel\n";}foreach(@camel1hump){chomp;$Camel=$_;y
/LJF7\173\175`\047/12345678/;y/12345678/JL7F\175\173\0 47`/;
$_=reverse;print"\040$_$Camel\n";}';;s/\s*//g;;eval; eval
("seek\040DATA,0,0;");undef$/;$_=<DATA>;s/\s*//g;( );;s
;^.*_;;;map{eval"print\"$_\"";}/.{4}/g; __DATA__ \124 \1
50\145\040\165\163\145\040\157\1 46\040\1 41\0 40\143\141 \155\145\1
54\040\1 51\155\ 141 \147\145\0 40\151\156 \040\141 \163\16 3\ 157\143\
151\141\16 4\151\1 57\156 \040\167 \151\164\1 50\040\ 120\1 45\162\
154\040\15 1\163\ 040\14 1\040\1 64\162\1 41\144 \145\ 155\14 1\162\
153\04 0\157 \146\ 040\11 7\047\ 122\1 45\15 1\154\1 54\171 \040 \046\
012\101\16 3\16 3\15 7\143\15 1\14 1\16 4\145\163 \054 \040 \111\156\14
3\056 \040\ 125\163\145\14 4\040\ 167\1 51\164\1 50\0 40\160\ 145\162
\155\151 \163\163 \151\1 57\156\056

Note that in the language that enforces indentation rules, the code
above would not be possible.

Regards

--
Mladen Gogala
Database Consultant
Tel: (347) 321-1217
https://dbwhisperer.wordpress.com