| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Zhihong Yu <zyu(at)yugabyte(dot)com>, gkokolatos(at)pm(dot)me, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)fujitsu(dot)com> |
| Subject: | Re: Allow batched insert during cross-partition updates |
| Date: | 2021-04-07 01:49:35 |
| Message-ID: | CA+HiwqHWQXp4W_AW8w+ZUUuzYxCNwYt31265JWMokh17vcv=Jg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 6, 2021 at 10:52 PM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
> On Tue, Apr 6, 2021 at 6:37 PM Amit Langote <amitlangote09(at)gmail(dot)com> wrote:
> > > 3) will the cmin in the output always be the same?
> > > +SELECT cmin, * FROM batch_cp_upd_test3;
> >
> > TBH, I am not so sure. Maybe it's not a good idea to rely on cmin
> > after all. I've rewritten the tests to use a different method of
> > determining if a single or multiple insert commands were used in
> > moving rows into foreign partitions.
>
> Thanks! It looks good!
Thanks for checking. I'll mark this as RfC.
--
Amit Langote
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2021-04-07 02:23:04 | Re: policies with security definer option for allowing inline optimization |
| Previous Message | Michael Paquier | 2021-04-07 01:20:31 | Re: Proposal: Save user's original authenticated identity for logging |