| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
| Subject: | Re: Inadequate executor locking of indexes |
| Date: | 2019-03-13 01:55:22 |
| Message-ID: | 23411878-a5c8-59f5-f30d-d2954bfe8ca2@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(this is not a reply to your full proposal, just something I thought to
point out)
On 2019/03/13 10:38, David Rowley wrote:
> i.e don't open the indexes for DELETEs. I had ideas that maybe this
> could be changed to check the idxlockmode and open the indexes if it's
> above AccessSharedLock. There didn't seem to be a very nice way to
> fetch the RangeTblEntry from the ResultRelInfo though,
Did you miss ri_RangeTableIndex? It's the range table index of the result
relation for which a given ResultRelInfo is created.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matsumura, Ryo | 2019-03-13 01:56:04 | RE: ECPG regression with DECLARE STATEMENT support |
| Previous Message | Jamison, Kirk | 2019-03-13 01:48:16 | RE: pg_upgrade: Pass -j down to vacuumdb |