| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: COPY and Volatile default expressions |
| Date: | 2013-04-15 16:35:32 |
| Message-ID: | 2292.1366043732@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Fetter <david(at)fetter(dot)org> writes:
> On Mon, Apr 15, 2013 at 05:04:16PM +0100, Simon Riggs wrote:
>> Loading data into a table with a SERIAL or UUID column is the main
>> use case, so I'll measure that.
> The former is common enough a use case to optimize specifically,
> should the numbers come out right.
Yeah. TBH I would rather see a special-case hack in the COPY code to
accept nextval() than expose anything as dirty and special-purpose as
this proposed flag to users. But in any case, I don't believe that
adequate evidence has been offered to show that we should do anything
at all here.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-04-15 16:50:26 | Re: WIP: index support for regexp search |
| Previous Message | Hannu Krosing | 2013-04-15 16:24:48 | Re: COPY and Volatile default expressions |