On Thu, Sep 08, 2005 at 05:35:40PM +0200, Bohdan Linda wrote:
> On Thu, Sep 08, 2005 at 04:35:51PM +0200, Michael Fuhr wrote:
> > On Thu, Sep 08, 2005 at 03:39:50PM +0200, Bohdan Linda wrote:
> > commit it now." You have to do some extra bookkeeping and you can't
> > commit several prepared transa
On Thu, Sep 08, 2005 at 04:35:51PM +0200, Michael Fuhr wrote:
> On Thu, Sep 08, 2005 at 03:39:50PM +0200, Bohdan Linda wrote:
> commit it now." You have to do some extra bookkeeping and you can't
> commit several prepared transactions atomically (as far as I know),
> but that's one way you could m
On Thu, Sep 08, 2005 at 03:39:50PM +0200, Bohdan Linda wrote:
> On Thu, Sep 08, 2005 at 02:53:47PM +0200, Michael Fuhr wrote:
> > One way would be to use contrib/dblink to open another connection
> > to the database so the status messages could be inserted in a
> > separate transaction.
>
> This c
On Thu, Sep 08, 2005 at 02:53:47PM +0200, Michael Fuhr wrote:
> One way would be to use contrib/dblink to open another connection
> to the database so the status messages could be inserted in a
> separate transaction.
This could do the trick for logging, even writting of a package that would
do al
On Thu, Sep 08, 2005 at 01:23:56PM +0200, Bohdan Linda wrote:
> plpgsq code does time intensive data manipulation + database vacuuming.
> This data manipulation is splitted logically into several steps. After
> each step I would like to give a message to the status table, what the
> procedure is pe
Hello,
I have read that 7.x version had a model "all or nothing" in transactions.
Thus I have upgraded to version 8 and would like to do the following:
plpgsq code does time intensive data manipulation + database vacuuming.
This data manipulation is splitted logically into several steps. After
