Re: [HACKERS] redolog - for discussion

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Jan Wieck <jwieck(at)debis(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] redolog - for discussion
Date: 1998-12-17 08:03:18
Message-ID: 3678BAC6.2124CA81@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jan Wieck wrote:
>
> >
> > I foresee problems with using _commands_ logging for
> > recovery/replication -:((
> >
...
>
> Yepp, the order in which commands begun is absolutely not of
> interest. Locking could already delay the execution of one
> command until another one started later has finished and
> released the lock. It's a classic race condition.
>
> Thus, my plan was to log the queries just before the call to
> CommitTransactionCommand() in tcop. This has the advantage,

Oh, I see - you right!

...
>
> Unfortunately query level logging get's hit by the current
> implementation of sequence numbers. If a query that get's
...
>
> All that is painful and I don't see another solution yet than
> to hook into nextval(), log out the numbers generated in

Not so bad, having buffering these numbers in memory...

> normal operation and getting back the same numbers in redo
> mode.
>
> The whole thing gets more and more complicated :-(

As usual -:))

Vadim

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Karl Eichwalder 1998-12-17 10:13:59 Re: Have any ideas to support GNU gettext package ??
Previous Message Vadim Mikheev 1998-12-17 06:14:39 Re: [HACKERS] MVCC works in serialized mode!