Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers

From: Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Nikhil Sontakke <nikkhils(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
Date: 2011-11-09 15:59:49
Message-ID: CABamaqNTm-wzDpHS+-XtQtNbb7eHSiSWJUkuJBGO8QoBDWwVhg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > Yeah thanks, that does the object locking. For pre-9.1 versions, we will
> > need a similar solution. I encountered the issue on 8.3.x..
>
> I don't think we should back-patch a fix of this type. There is a lot
> of cruftiness of this type scattered throughout the code base, and if
> we start back-patching all the fixes for it, we're going to end up
> destabilizing older branches for little real benefit.
>
>
Ok, understood.

Thanks and Regards,
Nikhils

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-11-09 16:00:09 Re: a modest improvement to get_object_address()
Previous Message Robert Haas 2011-11-09 15:58:50 Re: const correctness