Re: [HACKERS] [PATCH] Call RelationDropStorage() for broader range ofobject drops.
| От | Alexander Korotkov |
|---|---|
| Тема | Re: [HACKERS] [PATCH] Call RelationDropStorage() for broader range ofobject drops. |
| Дата | |
| Msg-id | CAPpHfds6c_a1kSL6u9B1_w3zJxYcoriQwVWpdCjc_CO6Qdih-g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] [PATCH] Call RelationDropStorage() for broader rangeof object drops. (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
| Ответы |
Re: [HACKERS] [PATCH] Call RelationDropStorage() for broader range ofobject drops.
|
| Список | pgsql-hackers |
On Thu, Sep 14, 2017 at 1:05 PM, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
Postgres Professional: http://www.
Hadi Moshayedi wrote:
> To provide more context, in cstore_fdw creating the storage is easy, we
> only need to hook into CREATE FOREIGN TABLE using event triggers. Removing
> the storage is not that easy, for DROP FOREIGN TABLE we can use event
> triggers.
This all sounds a little more complicated than it should ... but since
FDW are not really IMO the right interface to be implementing a
different storage format, I'm not terribly on board with supporting this
more completely. So what you're doing now is probably acceptable.
+1,
FDW looks OK for prototyping pluggable storage, but it doesn't seem suitable for permanent implementation.
BTW, Hadi, could you visit "Pluggable storage" thread and check how suitable upcoming pluggable storage API is for cstore?
------
Alexander KorotkovPostgres Professional: http://www.
The Russian Postgres Company
В списке pgsql-hackers по дате отправления: