| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Surafel Temesgen <surafel3000(at)gmail(dot)com>, alvherre(at)2ndquadrant(dot)com |
| Cc: | Adam Berlin <berlin(dot)ab(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: COPY FROM WHEN condition |
| Date: | 2018-12-12 18:28:29 |
| Message-ID: | 3b2b1aac-5861-acd8-fda3-054c4e4da888@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/12/18 7:05 AM, Surafel Temesgen wrote:
>
>
> On Tue, Dec 4, 2018 at 12:44 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com
> <mailto:alvherre(at)2ndquadrant(dot)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
| Attachment | Content-Type | Size |
|---|---|---|
| pEpkey.asc | application/pgp-keys | 8.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-12-12 20:00:03 | Bogus EPQ plan construction in postgres_fdw |
| Previous Message | Andres Freund | 2018-12-12 17:56:53 | Re: Reorganize collation lookup time and place |