| From: | Steve Singer <steve(at)ssinger(dot)info> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: logical changeset generation v6.5 |
| Date: | 2013-11-13 12:44:28 |
| Message-ID: | BLU0-SMTP709117745754B11138C3AADCF90@phx.gbl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/11/2013 02:06 PM, Andres Freund wrote:
> On 2013-11-10 14:45:17 -0500, Steve Singer wrote:
>
> Not really keen - that'd be a noticeable overhead. Note that in the
> cases where DEFAULT|INDEX is used, you can just use the new tuple to
> extract what you need for the pkey lookup since they now have the same
> format and since it's guaranteed that the relevant columns haven't
> changed if oldtup is null and there's a key.
>
> What are you actually doing with those columns? Populating a WHERE
> clause?
Yup building a WHERE clause
> Greetings,
>
> Andres Freund
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajeev rastogi | 2013-11-13 13:09:19 | Standalone synchronous master |
| Previous Message | Leonardo Francalanci | 2013-11-13 12:42:46 | Re: Fast insertion indexes: why no developments |