| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UPSERT on partition |
| Date: | 2015-06-29 09:36:23 |
| Message-ID: | 55911197.4020003@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-06-25 AM 09:51, Amit Langote wrote:
>
> Peter,
>
> On 2015-06-25 AM 02:35, Peter Geoghegan wrote:
>>
>> Inheritance with triggers is a leaky abstraction, so this kind of
>> thing is always awkward. Still, UPSERT has full support for
>> *inheritance* -- that just doesn't help in this case.
>>
>
> Could you clarify as to what UPSERT's support for inheritance entails?
>
Oh, I see that this stuff has been discussed (-hackers) and written about
(wiki). I'll go read about it.
I agree with Fujii-san's concern that any UPSERT on partition limitations
given those of partitioning approach should be documented likewise, if not
under INSERT/UPSERT, then under partitioning; not really sure which.
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-06-29 10:11:08 | Re: anole: assorted stability problems |
| Previous Message | Heikki Linnakangas | 2015-06-29 08:37:11 | Re: PANIC in GIN code |