Hi, knowing that "autonomous transaction" (Oracle
concept of) are not yet implemented in PostgreSQL, has
anyone found a work-around. I need to preserve
database states from a potential rollback and then log
them inside database tables.
What about:
1) using memory structures to hold the info, then
My understanding is that this feature won't be available even in v8 of
postgres. Nested transactions will roll back with the main transaction
when it's rolled back...
You could take a look at contrib/dblink because apparantly you can open
a connection to another (and probably the same) DB, an
At 11:18 AM -0400 9/13/04, Daniel Daoust wrote:
Hi, knowing that "autonomous transaction" (Oracle
concept of) are not yet implemented in PostgreSQL, has
anyone found a work-around. I need to preserve
database states from a potential rollback and then log
them inside database tables.
What I use for
Daniel Daoust <[EMAIL PROTECTED]> writes:
> Hi, knowing that "autonomous transaction" (Oracle
> concept of) are not yet implemented in PostgreSQL, has
> anyone found a work-around. I need to preserve
> database states from a potential rollback and then log
> them inside database tables.
Postgres
> You could take a look at contrib/dblink because
> apparantly you can open
>a connection to another (and probably the same)
> DB, and then write
> your logging information that way (ie within a
> function or session).
> Anything you do using the dblink will not be rolled
> back.
Superb! It
