Re^5: Perl Contempt in My Workplace

I can't find that in postgres docs, so it looks like you copied that from docs of an old version (version 9.4 is not even supported anymore) (this particular content is still true, though). Annoyingly, google often serves up old pages before more up-to-date ones.

(There is a 'current' link on top of every postgres doc page, and a link for all supported versions, as well as a link into the docs of the development branch, at the moment 14devel -- and btw: 14beta is expected in a few weeks)

Ah well...

Comment on Re^5: Perl Contempt in My Workplace

Replies are listed 'Best First'.
Re^6: Perl Contempt in My Workplace by hippo (Archbishop) on Apr 29, 2021 at 08:19 UTC
I can't find that in postgres docs, so it looks like you copied that from docs of an old version (version 9.4 is not even supported anymore) It was still there in the docs for version 10 (which is currently supported), although it does seem to be missing from later versions. I used duckduckgo to find this. 🦛	[reply]
Re^7: Perl Contempt in My Workplace by erix (Prior) on Apr 29, 2021 at 09:22 UTC
Well, as I said, the content of the text that I referred to (i.e., the text that bliako quoted) is still true but that text as quoted is in newer versions removed, rephrased, whatever you want to call it. I was just trying to get people to be aware that search engines throw up old postgresql documentation. It would be nice if here on perlmonks the URLs into the postgresql docs used the '/current/' unless old behaviour is specifically meant or targeted.	[reply]
Re^6: Perl Contempt in My Workplace by bliako (Abbot) on Apr 29, 2021 at 09:21 UTC
OK, I will wait a bit before striking out what I posted regarding Python or until you confirm that PL/Python is safe now. Thanks for the correction.	[reply]