From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-patches(at)postgreSQL(dot)org |
Subject: | Re: Values list-of-targetlists patch for comments (was Re: |
Date: | 2006-08-02 14:42:09 |
Message-ID: | 44D0B9C1.2020608@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers pgsql-patches |
Tom Lane wrote:
>
> I wonder whether there is any reasonable way to determine which data
> structures are responsible for how much space ... in my test I'm seeing
>
> MessageContext: 822075440 total in 104 blocks; 4510280 free (1 chunks); 817565160 used
> ExecutorState: 8024624 total in 3 blocks; 20592 free (12 chunks); 8004032 used
>
> so it seems mostly not the executor's fault, but that's not much to go
> on.
I was doing it by sprinkling MemoryContextStats() in various places.
I'll spend some time again later today and see if I can narrow it down
to specific data structures using that. It shouldn't be too hard -- the
patch I sent last night only pfrees a few structures, and they represent
the bulk of what we need to clean up.
Joe
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-08-02 15:56:23 | Re: Values list-of-targetlists patch for comments (was Re: |
Previous Message | Tom Lane | 2006-08-02 14:25:08 | Re: Values list-of-targetlists patch for comments (was Re: |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Hammond | 2006-08-02 15:52:20 | Re: Replication Documentation |
Previous Message | Andrew Dunstan | 2006-08-02 14:25:33 | Re: ecpg test suite |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Hammond | 2006-08-02 15:52:20 | Re: Replication Documentation |
Previous Message | Tom Lane | 2006-08-02 14:25:08 | Re: Values list-of-targetlists patch for comments (was Re: |