| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY and Volatile default expressions |
| Date: | 2014-01-15 15:47:45 |
| Message-ID: | CA+U5nM+6b_fT=FeW-SgwcOJsOrxWevAbeG4wYW0RP6N4L6+Frg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 April 2013 14:37, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 16 April 2013 13:57, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> wrote:
>
>> You still need to check the args, if the function is nextval, otherwise you
>> incorrectly perform the optimization for something like
>> "nextval(myvolatilefunc())".
>
> Guess so. At least its an easy change.
>
> Thanks for checking.
Rebased v3
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| copy_tuning_with_default_nextval.v3.patch | application/octet-stream | 6.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mel Gorman | 2014-01-15 15:53:45 | Re: [Lsf-pc] Linux kernel impact on PostgreSQL performance |
| Previous Message | Andres Freund | 2014-01-15 15:22:19 | Re: shared memory message queues |