Re: Proposed Resource Manager Changes - Mailing list pgsql-hackers

From ITAGAKI Takahiro
Subject Re: Proposed Resource Manager Changes
Date
Msg-id 20080820101615.8832.52131E4D@oss.ntt.co.jp
Whole thread Raw
In response to Proposed Resource Manager Changes  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Proposed Resource Manager Changes  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Proposed Resource Manager Changes  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> wrote:

> I would like to make a simple change to Resource Manager code to
> introduce a plugin that can redefine or extend Rmgrs.

It looks very reasonable to me.

> * values 33-127 are available by centrally managed registration to help
> avoid conflicts in Postgres projects on pgfoundry
> * values 128+ are user defined

One thing to worry about is a confliction of RmgrId. We can check
conflictions in redo because rmgrs are actually registered, but
we might need to check conflictions even in a normal running.
Extensions that write own XLog record can use arbitrary RmgrIds without
restrictions. It would be safe if we check whether RmgrIds required by
extensions are actually unused.

For more safe, we could store signatures of extensions in control file.
We store mapping of RmgrId to signatures in it and checks no changes since
last shutdown. UUID types (128 bits) would be good for the signature.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch: plan invalidation vs stored procedures
Next
From: Tom Lane
Date:
Subject: Re: Patch: plan invalidation vs stored procedures