Re: Auto-delete large objects when referencing row is deleted
От | higepon |
---|---|
Тема | Re: Auto-delete large objects when referencing row is deleted |
Дата | |
Msg-id | f07386410904071917p4f36d16aoee04794a9c52ba40@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Auto-delete large objects when referencing row is deleted (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Auto-delete large objects when referencing row is deleted
|
Список | pgsql-hackers |
Hi > I assume you mean $subject and not what you wrote here. Yes. Sorry it's my mistake. >> I examined contrib/lo which offers this functionality. > > Yes. I wonder why the TODO item is there at all, when contrib/lo > already solves it in a perfectly reasonable way. As a user of database, I think contrib/lo is not the best way. Because it's not a part of core PostgreSQL, users may forget to use them. Or it is a little messy to use. So I think we need to implement *Auto* delete functionality in PostgreSQL core. Cheers. ----- Taro Minowa(Higepon) Cybozu Labs, Inc. http://www.monaos.org/ http://code.google.com/p/mosh-scheme/ On Mon, Apr 6, 2009 at 11:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > higepon <higepon@gmail.com> writes: >> I found a TODO item "pg_dump Add dumping of comments on index columns" >> for large objects. >> and want to write a patch for it. > > I assume you mean $subject and not what you wrote here. > >> I examined contrib/lo which offers this functionality. > > Yes. I wonder why the TODO item is there at all, when contrib/lo > already solves it in a perfectly reasonable way. > > regards, tom lane >
В списке pgsql-hackers по дате отправления: