| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: tuplesort memory usage: grow_memtuples |
| Date: | 2012-10-18 16:04:41 |
| Message-ID: | CAEYLb_XKBTBr-iN-hvhW9yef4jNcYB6zRpoqLYgqYgaQFHyA0Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 October 2012 21:47, Peter Geoghegan <peter(at)2ndquadrant(dot)com> wrote:
> The same basic strategy for sizing the tuplesort memtuples array in
> also exists in tuplestore. I wonder if we should repeat this there? I
> suppose that that could follow later.
Incidentally, the basis of this remark is commit 2689abf0, where Tom
decided to keep the two in sync. That's a precedent for what we need
to do here, I suppose.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2012-10-18 16:07:45 | Re: [PATCH 3/8] Add support for a generic wal reading facility dubbed XLogReader |
| Previous Message | Alvaro Herrera | 2012-10-18 16:02:53 | Re: PATCH: pgbench - aggregation of info written into log |