How to don't use PL/pgSQL and other fatal errors when PL/pgSQL is used
I wrote article Jak nepoužívat PL/pgSQL (případně PL/SQL) – fatální chyby při vývoji. The article is in Czech language, but google translator can be used.
Some notes about PostgreSQL
I wrote article Jak nepoužívat PL/pgSQL (případně PL/SQL) – fatální chyby při vývoji. The article is in Czech language, but google translator can be used.
I did one indicative benchmark of popular interpret languages, and I was surprised how modern PHP is fast now. This test is pretty simple and stupid, syntactical, unrealistic, and I know it. It say nothing about speed any interpret in practical usage. But can be interesting to see, how surprisingly some interprets are near to C, and what engines can be used for intensive numeric calculations.
void main() { long int s = 0; int i; for (i 0; i < 10000000; i++) s := i; printf("%ld\n", s); }
optimized C | 3ms |
LuaJIT | 20ms |
unoptimized C | 30ms |
Lua | 100ms |
PHP | 200ms |
JavaScript V8 engine | 500ms |
Perl | 600ms |
JavaScrip Mozilla | 900ms |
Python2 | 1200ms |
Python3 | 1700ms |
PostgreSQL SQL | 1700ms |
PLpgSQL | 2200ms |
I finished all work on CUA menu (menubar and pulldown menu) ncurses library. This library allows skins, shadows, supports accelerators, mouse. Look to demo.c for info about usage. Download from Github.
I finished technology demo of ncurses based implementation of CUA menu - menubar and pull down menu. Please, check my github project https://github.com/okbob/ncurses-st-menu. I like when interface looking well - so I implemented few styles (owns styles are possible). You can see screenshots:
My presentation from last PostgreSQL meetup - https://postgres.cz/files/plpgsql_issues.pdf