Robert Treat <[EMAIL PROTECTED]> writes:
> On Fri, 2003-01-17 at 14:32, Tom Lane wrote:
>> Getting at objects in other databases is considerably less practical
>> than anything we've discussed here.

> Perhaps you don't allow the removal unless all databases came up clean.
> You can have the db admin go in a clean up each database manually if
> need be. Granted this doesn't solve getting at those other databases in
> the first place, but it eliminates any transactional issues.

Oh?  What if someone creates an object belonging to the user after we've
finished examining that database?  (Actually, this issue exists even
within a single database; so I suppose we'd need to invent some kind of
lock on userids ...)

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Reply via email to