RE: [HACKERS] 7.0 status request

> -----Original Message-----
> From: owner-pgsql-hackers(at)postgreSQL(dot)org
> [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Tom Lane
> Sent: Friday, November 19, 1999 4:03 PM
> To: Bruce Momjian
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] 7.0 status request
>
> I think there are also a lot of unresolved questions about interlocking
> and updating of the catalog caches and relcache. These might be
> must-fix items. IIRC, Hiroshi is pretty concerned about that area...
>

Unfortunately I don't have a reasonable solution for interlocking yet.
First,row level locking for system tuples not only exclusive but
also shared will be needed. I couldn't find the way to implement
shared row level locking now.
Moreover I'm suspicious that this row level locking could be used
for parser/planner. Row level locking(at least in current implemen
tation) is held till end of transaction.

As for cache invalidation(rollback),I may be able to do something.
However new save point feature would need some change around
it. I don't know how Vadim would change it.

Regards.

Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp