Re: [BUGS] BUG #8573: int4range memory consumption
От | Robert Haas |
---|---|
Тема | Re: [BUGS] BUG #8573: int4range memory consumption |
Дата | |
Msg-id | CA+TgmoYYmSg5+61Yrg9PeyQ0k-JQv+BTnwu-k+ezs81B92axug@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #8573: int4range memory consumption (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On Mon, Nov 4, 2013 at 10:51 PM, Amit Kapila <amit.kapila16@gmail.com> wrote: > On Tue, Nov 5, 2013 at 12:52 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Amit Kapila <amit.kapila16@gmail.com> writes: >>> On Mon, Nov 4, 2013 at 8:15 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >>>> Really I'd like to see standalone mode, in its current form, go away >>>> completely. I had a prototype patch for allowing psql and other clients >>>> to interface to a standalone backend. I think getting that finished would >>>> be a way more productive use of time than improving debugtup. >> >>> The last patch including Windows implementation was posted at below >>> link sometime back. >>> http://www.postgresql.org/message-id/6C0B27F7206C9E4CA54AE035729E9C382853263C@szxeml509-mbs >> >>> If this is the right thing, I can rebase the patch and make it ready. >> >> IIRC, the discussion stalled out because people had security concerns >> and/or there wasn't consensus about how it should look at the user level. >> There's probably not much point in polishing a patch until we have more >> agreement about the high-level design. > > Okay. However +1 for working on that idea as lot of people have shown > interest in it. Agreed. I remember the sticking point as being mostly, like, whether we should just make it work, or whether we had to do a huge amount of additional work to turn it into something quite different from what you had in mind. That question answers itself. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: