From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Mikko Partio <mpartio(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: SPI-functions and transaction control |
Date: | 2008-02-18 22:12:27 |
Message-ID: | 20080218221227.GG11594@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Mikko Partio escribió:
> Now, I was wondering if a c function would be faster, and with the help of
> the manual I have written a function that can insert tuples from one table
> to another. As the manual states (
> http://www.postgresql.org/docs/8.3/interactive/spi.html) there is no way to
> catch the constraint violation error with SPI though. The manual still
> mentions that there is an undocumented way of doing this, has anybody ever
> done this? I was looking the 'exception' code at
> src/pl/plpgsql/src/pl_exec.c but it's quite frightening since I really don't
> have that much experience in c :)
I think you should try DefineSavepoint, RollbackToSavepoint and
ReleaseSavepoint. Take a close look at plpgsql's callers for those
functions, because I don't think it's all that straightforward. OTOH
you also need some PG_TRY blocks. There are many fine details here,
perhaps too many if you're not battered enough in C.
I think I would suggest trying to do it purely with SQL, temp tables,
etc. If you can afford a table lock, it could be a lot easier and
faster than setting a savepoint per tuple.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-02-18 22:35:10 | Re: Pains in upgrading to 8.3 |
Previous Message | Tom Lane | 2008-02-18 21:58:04 | Re: [HACKERS] deadlock with truncate and foreing keys |