| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: can we optimize STACK_DEPTH_SLOP |
| Date: | 2016-07-07 00:01:11 |
| Message-ID: | CAM-w4HMiJKdjX=7SZj5OTtK7-VkznVbwsC1km=4X=Y0=0rej2w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Ok, I managed to get __atribute__((destructor)) working and capitured
the attached pmap output for all the revisions. You can see the git
revision in the binary name along with a putative date though in the
case of branches the date can be deceptive. It looks to me like REL8_4
is already bloated by REL8_4_0~2268 (which means 2268 commits *before*
the REL8_4_0 tag -- i.e. soon after it branched).
I can't really make heads or tails of this. I don't see any commits in
the early days of 8.4 that could change the stack depth in the
postmaster.
| Attachment | Content-Type | Size |
|---|---|---|
| pmap.txt | text/plain | 2.1 MB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-07-07 01:45:36 | Re: can we optimize STACK_DEPTH_SLOP |
| Previous Message | Stephen Frost | 2016-07-06 23:03:33 | Re: dumping database privileges broken in 9.6 |