Re: PL/pgSQL: EXCEPTION NOSAVEPOINT
От
Christopher Kings-Lynne
Тема
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT
Дата
Msg-id
4317A80B.9080807@familyhealth.com.au
Ответ на
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT (Matt Miller)
Список
Дерево обсуждения
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Matt Miller <mattm@epx.com>
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Josh Berkus <josh@agliodbs.com>
Re: Ora2Pg (was PL/pgSQL: EXCEPTION NOSAVEPOINT) Matt Miller <mattm@epx.com>
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Matt Miller <mattm@epx.com>
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Tom Lane <tgl@sss.pgh.pa.us>
Re: PL/pgSQL: EXCEPTION NOSAVEPOINT Tom Lane <tgl@sss.pgh.pa.us>
Why don't you just use EnterpriseDB? Chris > That would defeat my goal of not rewriting all my Oracle code. > > If I were fool enough to plan an attack on the main executor's exception > handling to try and disarm it of its subtransaction semantics, where > would I start? Where would I end? What would I do in between? Can New > Orleans be rebuilt above sea level? > > Seriously, though, I'm willing to devote considerable time to this. > Rewriting all my Oracle code function-by-function could be painful, and > I would end up dragging other people around this company into it. I'm > still trying to hold on to my fantasy that I can hack Postgres (and > contrib/ora2pg) into submission. In the end I'm hoping that the move > from Oracle will be made easier for others. > > ---------------------------(end of broadcast)--------------------------- > TIP 5: don't forget to increase your free space map settings
В списке pgsql-hackers по дате отправления