| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Subject: | Re: Add parallelism and glibc dependent only options to reindexdb |
| Date: | 2019-07-16 12:03:16 |
| Message-ID: | CAOBaU_bHvyVPrm0UZNiJOmSCJ7p5DHZi9O+Q1pk8Gy-oRmY02A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 12, 2019 at 11:47 AM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>
> I didn't change the behavior wrt. possible deadlock if user specify
> catalog objects using --index or --table and ask for multiple
> connection, as I'm afraid that it'll add too much code for a little
> benefit. Please shout if you think otherwise.
Sorry I meant schemas, not indexes.
After more thinking about schema and multiple jobs, I think that
erroring out is quite user unfriendly, as it's entirely ok to ask for
multiple indexes and multiple object that do support parallelism in a
single call. So I think it's better to remove the error, ignore the
given --jobs options for indexes and document this behavior.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-07-16 12:39:43 | Re: refactoring - share str2*int64 functions |
| Previous Message | Masahiko Sawada | 2019-07-16 11:56:32 | Re: Resume vacuum and autovacuum from interruption and cancellation |