Re: [HACKERS] RustgreSQL
От | Jim Nasby |
---|---|
Тема | Re: [HACKERS] RustgreSQL |
Дата | |
Msg-id | 9ef81dc2-0659-4a1b-3d74-f4797994e965@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] RustgreSQL (Pavel Stehule <pavel.stehule@gmail.com>) |
Список | pgsql-hackers |
On 1/9/17 3:15 AM, Pavel Stehule wrote: > The running unsafe PL in own managed processes is good idea - Years, I > have a one diploma theme "better management of unsafe PL in Postgres" - > but still without any interest from students :(. I had two > possibilities to see catastrophic errors related to wrong usage of > PLPerlu. If we can locks interpret/environment in some safe sandbox, > then it should be great. Incidentally, Tom just observed in another thread that Tcl treats out of memory as a panic situation, so anyone using pltcl opens the risk of arbitrary database-wide panics. Fenced pltcl is one possible solution for that problem. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532)
В списке pgsql-hackers по дате отправления: