From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 大塚憲司 <otsuka(dot)kenji(at)nttcom(dot)co(dot)jp>, pgsql-docs(at)postgresql(dot)org, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] The number of bytes is stored in index_size of pgstatindex() ? |
Date: | 2016-02-19 20:02:24 |
Message-ID: | CAM3SWZQofb+vrCn2Xb9HVDfesWVEE7S3Q_xmriaAMfjbCJYPtQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On Thu, Feb 18, 2016 at 4:53 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Only a physical-order scan, ie vacuum, would visit a dead page
> (ignoring transient corner cases like a page getting deleted while an
> indexscan is in flight to it). So I think treating it as part of the
> fragmentation measure is completely wrong: the point of that measure,
> AFAICS, is to model how close an index-order traversal is to linear.
> Half-dead pages are also normally very transient --- the only way they
> persist is if there's a crash partway through a page deletion. So I think
> it's appropriate to assume that future indexscans won't visit those,
> either.
Okay.
>> there are usage patterns where half-dead pages might accumulate.
>
> Other than a usage pattern of "randomly SIGKILL backends every few
> seconds", I don't see how that would happen.
I meant where pages could accumulate without being recycled.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-02-19 20:05:44 | Re: [DOCS] The number of bytes is stored in index_size of pgstatindex() ? |
Previous Message | Tom Lane | 2016-02-19 00:53:53 | Re: [HACKERS] The number of bytes is stored in index_size of pgstatindex() ? |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-02-19 20:05:44 | Re: [DOCS] The number of bytes is stored in index_size of pgstatindex() ? |
Previous Message | Tom Lane | 2016-02-19 19:58:12 | Re: Restructuring Paths to allow per-Path targetlist info |