| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UPSERT on partition |
| Date: | 2015-06-26 22:35:10 |
| Message-ID: | 558DD39E.9020807@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/24/15 1:03 PM, Peter Geoghegan wrote:
> On Wed, Jun 24, 2015 at 11:02 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> I think that the real way to fix this is, as you say, to make it so
>> that it isn't necessary in general to write trigger functions like
>> this to make inheritance work.
>
> Excuse me -- I mean to make *partitioning* work.
It occurs to me that we could run the BEFORE triggers and then pass the
new tuple to a user-supplied function that returns a regclass. That
would allow us to know exactly which child/partition the UPSERT should
be attempted in.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-06-26 22:38:39 | Re: Re: [COMMITTERS] pgsql: psql: show proper row count in \x mode for zero-column output |
| Previous Message | Jim Nasby | 2015-06-26 22:30:07 | Re: pg_stat_*_columns? |