| From: | Robert DiFalco <robert(dot)difalco(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Insert vs Update |
| Date: | 2015-07-15 19:49:31 |
| Message-ID: | CAAXGW-zYODy0yjmgTR9OHNEZm_4LLLrJ4ZnmXPBrSVx=n8EwBQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Jul 15, 2015 at 12:32 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> You may be able to put Table Inheritance to good use here...
>
> I do not know (but doubt) if HOT optimization works when going from NULL
> to non-NULL since the former is stored in a bitmap while the later occupies
> normal relation space and thus the update would likely end up writing an
> entirely new record upon each event category recording.
>
> David J.
>
>
>
Thanks!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Nolan | 2015-07-15 20:53:10 | Re: Insert vs Update |
| Previous Message | David G. Johnston | 2015-07-15 19:32:18 | Re: Insert vs Update |