| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Nicola Contu <nicola(dot)contu(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Ray O'Donnell" <ray(at)rodonnell(dot)ie>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, Alessandro Aste <Alessandro(dot)aste(at)gtt(dot)net> |
| Subject: | Re: Performance comparison between Pgsql 10.5 and Pgsql 11.2 |
| Date: | 2019-03-05 16:47:07 |
| Message-ID: | CA+hUKGK-79u7t2q1ERLstVtboLF-i1EneSLacC2Wxr_U9tJVoQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Mar 6, 2019 at 4:22 AM Nicola Contu <nicola(dot)contu(at)gmail(dot)com> wrote:
>
> Not sure what you are requesting exactly but here is the strace for the start of the pg_ctl
I meant that you could run the server itself in the foreground under
strace, like so:
$ strace -f -c /usr/local/pgsql11.2/bin/postgres -D /db/pgsql11/data/
Then perform your testing, and finally stop it with pg_ctl from
another window (or hit ^C in this window) and strace should spit out a
table of system calls with some counters. We might be able to see why
v11 is spending so much more time executing system calls than v10 for
your workload, or at least which systems calls they are, assuming you
run the same transactions against both versions.
--
Thomas Munro
https://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2019-03-05 16:51:46 | Re: [External] LIMIT not showing all results |
| Previous Message | Tom Lane | 2019-03-05 16:46:18 | Re: [External] LIMIT not showing all results |