On 2018-08-17 15:21:19 +0200, Alexis Lê-Quôc wrote:
> On Tue, Aug 14, 2018 at 7:50 PM Andres Freund wrote:
>
> > Hi,
> >
> > On 2018-08-14 10:46:45 -0700, Andres Freund wrote:
> > > On 2018-08-14 15:18:55 +0200, Alexis Lê-Quôc wrote:
> > > > + 30.25%26.78% postgres postgres [.]
On Tue, Aug 14, 2018 at 7:50 PM Andres Freund wrote:
> Hi,
>
> On 2018-08-14 10:46:45 -0700, Andres Freund wrote:
> > On 2018-08-14 15:18:55 +0200, Alexis Lê-Quôc wrote:
> > > + 30.25%26.78% postgres postgres [.] mdnblocks
> >
> > This I've likely fixed ~two years back:
> >
> >
Hi,
On 2018-08-14 10:46:45 -0700, Andres Freund wrote:
> On 2018-08-14 15:18:55 +0200, Alexis Lê-Quôc wrote:
> > + 30.25%26.78% postgres postgres [.] mdnblocks
>
> This I've likely fixed ~two years back:
>
> http://archives.postgresql.org/message-id/72a98a639574d2e25ed946528485
Hi,
On 2018-08-14 15:18:55 +0200, Alexis Lê-Quôc wrote:
> We run
> a cluster of
> large, SSD-backed, i3.16xl (64 cores visible to Linux, ~500GB of RAM, with
> 8GB of shared_buffers, fast NVMe drives) nodes
> , each
> running PG 9.3
> on linux
> in a vanilla streaming asynchronous replication setup
On Tue, Aug 14, 2018 at 9:18 AM, Alexis Lê-Quôc wrote:
>
each
running PG 9.3
on linux
That is the oldest version which is still supported. There have been a lot
of improvements since then, including to performance. You should see if an
upgrade solves the problem. If not, at least you will
