Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers

Поиск
Список
Период
Сортировка
От Nikhil Sontakke
Тема Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
Дата
Msg-id CANgU5ZfOCMyu+E=u1Nwj0+HchgGa01-oPP4pysaer_ZqQHuWPQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Concurrent CREATE TABLE/DROP SCHEMA leaves inconsistent leftovers
Список 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 по дате отправления: