From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin Grittner <kgrittn(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: _mdfd_getseg can be expensive |
Date: | 2016-07-01 02:08:51 |
Message-ID: | 20160701020851.4ln3bdjwjhfmivje@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2016-06-30 18:34:20 -0700, Peter Geoghegan wrote:
> On Thu, Jun 30, 2016 at 6:23 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I plan to, once the tree opens again. Likely needs some considerable
> > updates for recent changes.
>
> Offhand, do you think that CREATE INDEX calls to smgrextend() could be
> appreciably affected by this bottleneck? If that's a very involved or
> difficult question, then no need to answer now.
If you have a big enough index (maybe ~150GB+), sure. Before that,
probably not.
It's usually pretty easy to see in cpu profiles whether this issue
exists.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2016-07-01 02:08:57 | Re: OpenSSL 1.1 breaks configure and more |
Previous Message | Michael Paquier | 2016-07-01 01:56:51 | Re: Is a UDF binary portable across different minor releases and PostgreSQL distributions? |