Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers - Mailing list pgsql-hackers

From Nikhil Sontakke
Subject Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
Date
Msg-id CANgU5ZfOCMyu+E=u1Nwj0+HchgGa01-oPP4pysaer_ZqQHuWPQ@mail.gmail.com
Whole thread Raw
In response to Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
List pgsql-hackers

 
So it's probably going to take a while to get this
completely nailed down, but we can keep chipping away at it.


Agreed. So are you planning to commit this change? Or we want some more objects to be fixed? Last I looked at this, we will need locking to be done while creating tables, views, types, sequences, functions, indexes, extensions, constraints, operators stuff, ts stuff, rules, domains, etc. that can go into schemas.

So might even make sense to write a schema specific function based on your patch template to cater in general to schema locking during object creation.

Regards,
Nikhils

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Regression tests fail once XID counter exceeds 2 billion
Next
From: Greg Smith
Date:
Subject: CommitFest 2011-11 starting soon