| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Shaozhong SHI <shishaozhong(at)gmail(dot)com>, Ludwig Isaac Lim <ludz_lim(at)yahoo(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: print in plpython not appearing in logs |
| Date: | 2022-12-14 01:21:52 |
| Message-ID: | 82cb253b-aabf-e7f1-90ba-82a4ef9350c1@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/13/22 13:20, Shaozhong SHI wrote:
> What is brilliant about plpython? Any brilliant examples to look at?
>
1) It is actually plython(3)u where the u means untrusted. This means
you can reach outside the database and do things. That can seen as
brilliant or dangerous.
2) You have no end of Python libraries you can work with. Again combined
with 1) up you whether that is brilliant or dangerous.
3) Python is more dynamic then plpgsql so you can get more adventurous
with doing dynamic SQL.
Downside is that plpython(3)u is not tied as closely to SQL as plpgsql
so it very often takes you many more lines of code to get something done.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yang, T. Andy | 2022-12-14 04:55:53 | compiling postgres on windows - how to deal with unmatched file extension? |
| Previous Message | Zheng Li | 2022-12-13 22:25:48 | Re: Support logical replication of DDLs |