| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY and Volatile default expressions |
| Date: | 2013-04-16 15:43:59 |
| Message-ID: | CA+U5nMLOA7EADwMjpS+OoWpvJQNPDYVaexVGY-kY6DFkL8t_pA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16 April 2013 15:07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> I found Simon's nextval()/COPY timings without this patch sobering. I
>> assume he can apply this for 9.3, right? I believe it is a fix for a
>> new 9.3 feature.
>
> It is not a "fix", it is not for a 9.3 feature (the multi-insert thing
> went in in 9.2), and personally I'd vote against applying it now,
> especially if Simon is expecting anybody to review it.
I wrote this expecting it to be a 9.4 feature. I'm good with that.
There are other somewhat related optimisations also.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2013-04-16 17:45:39 | Re: Enabling Checksums |
| Previous Message | Nigel Heron | 2013-04-16 15:07:44 | Re: currval and DISCARD ALL |