| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp>, Andres Freund <andres(at)anarazel(dot)de>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: ON CONFLICT DO UPDATE for partitioned tables |
| Date: | 2018-04-18 13:40:07 |
| Message-ID: | 20180418134007.n7vbkwww4e22sg6k@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Langote wrote:
> On 2018/04/18 0:04, Alvaro Herrera wrote:
> > Amit Langote wrote:
> >
> >> I just confirmed my hunch that this wouldn't somehow do the right thing
> >> when the OID system column is involved. Like this case:
> >
> > This looks too big a patch to pursue now. I'm inclined to just remove
> > the equalTupdesc changes.
>
> OK. Here is the patch that removes equalTupdesc optimization.
Hmm. If we modify (during pg12, of course -- not now) partition tables
that are created identical to their parent table so that they share the
pg_type row, this would become useful. Unless there a reason why that
change is completely unworkable, I'd just leave it there. (I claim that
it works like that only because it used to work like that, not because
it's impossible to make work the other way.)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2018-04-18 13:41:19 | Re: Built-in connection pooling |
| Previous Message | Alvaro Herrera | 2018-04-18 13:36:57 | Re: VM map freeze corruption |