| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, David Fetter <david(at)fetter(dot)org>, Rahila Syed <rahila(dot)syed(at)2ndquadrant(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: monitoring CREATE INDEX [CONCURRENTLY] |
| Date: | 2019-03-29 19:28:37 |
| Message-ID: | 20190329192837.GA3633@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Mar-29, Robert Haas wrote:
> On Fri, Mar 29, 2019 at 2:16 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > I think we should consider a new column of an array type, where we could
> > put things like the list of PIDs to be waited for, the list of OIDs of
> > index to rebuild, or the list of partitions to build the index on.
>
> This has to work with a fixed-size chunk of shared memory.
Bah, of course.
Maybe we can consider using dynamic shmem for that, and include a
pointer to it in the fixed-size chunk. (It's a bit too late to be
writing this code, mind; I'm just proposing this for a future
improvement.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2019-03-29 19:32:57 | Re: PostgreSQL pollutes the file system |
| Previous Message | Bernd Helmle | 2019-03-29 19:25:41 | Re: Enable data checksums by default |