> -----Original Message-----
> From: owner-pgsql-hackers(at)postgreSQL(dot)org
> [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Vadim Mikheev
> Sent: Thursday, December 17, 1998 5:03 PM
> To: Jan Wieck
> Cc: pgsql-hackers(at)postgreSQL(dot)org
> Subject: Re: [HACKERS] redolog - for discussion
> 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!
If image level logging is used,probably it's OK.
But if query(command) level logging is used ???
If the isolation level of all transactions is SERIARIZABLE,it's probably
OK because they are serializable order by the time when they are
But if there are transactions whose isolation level is READ COMMITTED,
they are not serializable.
So commands must be issued according to the original order when they
were issued ?
If the same mechanism of locking is used at recovery time,the order
of locks caused by commands(rerun) will be same ?????
I'm not confident.
In response to
pgsql-hackers by date
|Next:||From: Keith Parks||Date: 1998-12-18 01:16:41|
|Subject: Re: [HACKERS] CURRENT: crash in select_view regression test...|
|Previous:||From: Jan Wieck||Date: 1998-12-17 22:44:42|
|Subject: Re: [HACKERS] CVS log for a specific tag|