| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Cc: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Kevin Grittner <kgrittn(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Robert Haas <robert(dot)haas(at)enterprisedb(dot)com>, "pgsql-committers(at)postgresql(dot)org" <pgsql-committers(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Add the "snapshot too old" feature |
| Date: | 2016-04-12 18:59:06 |
| Message-ID: | 20160412185906.gx6qosdnag2efhgt@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2016-04-12 13:57:26 -0500, Kevin Grittner wrote:
> I have booked two large NUMA machines for Friday to look for any
> remaining performance regressions on high-concurrency loads on such
> machines. Anyone with ideas on particular tests that they feel
> should be included, please let me know before then.
The worst case is probably statements which are utterly trivial to
execute, but do require a snapshot both during planning and
execution. Like e.g. SELECT 1;. That's probably a good thing to get
started with.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Piotr Stefaniak | 2016-04-12 19:13:39 | Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
| Previous Message | Kevin Grittner | 2016-04-12 18:57:26 | Re: pgsql: Add the "snapshot too old" feature |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Piotr Stefaniak | 2016-04-12 19:13:39 | Re: [COMMITTERS] pgsql: Allow Pin/UnpinBuffer to operate in a lockfree manner. |
| Previous Message | Kevin Grittner | 2016-04-12 18:57:26 | Re: pgsql: Add the "snapshot too old" feature |