| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Delay locking partitions during query execution |
| Date: | 2019-01-30 23:21:49 |
| Message-ID: | CAKJS1f_420wKMVWLz9xBr94T_5n0yzrrG2_9wk-aZGUPLGFrxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 29 Jan 2019 at 19:42, Amit Langote
<Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> However, I tried the example as you described and the plan *doesn't*
> change due to concurrent update of reloptions with master (without the
> patch) either.
Well, I didn't think to try that. I just assumed had broken it.
Could well be related to lowering the lock levels on setting these
reloptions. Once upon a time, they required an AEL but that was
changed in e5550d5fec6. So previous to that commit you'd have been
blocked from making the concurrent change while the other session was
in a transaction.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Elvis Pranskevichus | 2019-01-30 23:35:25 | Re: [PATCH] Allow anonymous rowtypes in function return column definition |
| Previous Message | Tom Lane | 2019-01-30 22:59:41 | Re: [PATCH] Allow anonymous rowtypes in function return column definition |