Re: COPY and Volatile default expressions

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
Cc: 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: 2013-04-16 11:38:16
Message-ID: CA+U5nM+P_MMK7X4CqAszqdrgHLvAZpNK1dS9=yp2T6upn9E9qg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 15 April 2013 21:53, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:

> So I'll treat this as two separate cases:
> * add special case for sequences

Patch attached.

> * use the NO SQL mechanism, as described, which implies no reads or
> writes of database state. We could test that, but its somewhat harder
> and we'd need to test for that on entry to any function, which I don't
> much like.

For another time.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
copy_tuning_with_default_nextval.v1.patch application/octet-stream 6.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-04-16 11:49:47 Re: event trigger API documentation?
Previous Message Colin 't Hart 2013-04-16 09:40:16 [PATCH] Add \ns command to psql