Re: [BUGS] BUG #8573: int4range memory consumption - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [BUGS] BUG #8573: int4range memory consumption
Date
Msg-id 26505.1383592953@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] BUG #8573: int4range memory consumption  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [BUGS] BUG #8573: int4range memory consumption  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
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.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: pgsql: Remove internal uses of CTimeZone/HasCTZSet.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Remove internal uses of CTimeZone/HasCTZSet.