Re: COPY FROM WHEN condition

Tomas Vondra <tomas.vondra@2ndquadrant.com>

View thread View on postgr.es

From: Tomas Vondra <tomas.vondra@2ndquadrant.com>

To: Surafel Temesgen <surafel3000@gmail.com>, alvherre@2ndquadrant.com

Cc: Adam Berlin <berlin.ab@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2018-12-12T18:28:29Z

Lists: pgsql-hackers

Attachments

pEpkey.asc (application/pgp-keys)


On 12/12/18 7:05 AM, Surafel Temesgen wrote:
> 
> 
> On Tue, Dec 4, 2018 at 12:44 PM Alvaro Herrera <alvherre@2ndquadrant.com
> <mailto:alvherre@2ndquadrant.com>> wrote:
> 
>     After reading this thread, I think I like WHERE better than FILTER.
>     Tally:
> 
>     WHERE: Adam Berlin, Lim Myungkyu, Dean Rasheed, yours truly
>     FILTER: Tomas Vondra, Surafel Temesgen
> 
> 
> 
> accepting tally result  i change the keyword to WHERE condition and
> allow volatile function with single insertion method

Can you also update the docs to mention that the functions called from
the WHERE clause does not see effects of the COPY itself?

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

Remove unused struct member, enforce multi_insert callback presence.
- 57a7a3adfe4e 12.0 landed
Separate per-batch and per-tuple memory contexts in COPY
- 36a1281f86c0 12.0 landed
Fix handling of volatile expressions in COPY FROM ... WHERE
- 4a8283d0ec5a 12.0 landed
Allow COPY FROM to filter data using WHERE conditions
- 31f3817402da 12.0 landed
Remove obsolete netbsd dynloader code
- b68ff3ea672c 12.0 cited