Re: [PATCH] COPY vs \copy HINT

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] COPY vs \copy HINT
Date: 2016-09-05 01:08:11
Message-ID: CAMsr+YHN_gp6nAAtZ9WZYS5DUwzsbfJGoAQFQnJfrr5a8S4zog@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5 September 2016 at 09:05, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:

>I've attached an update that does so and
> warns on EACCES too.

... this time, with required parens.

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

Attachment Content-Type Size
0001-Emit-a-HINT-when-COPY-can-t-find-a-file.patch text/x-patch 2.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-09-05 01:09:41 Re: Remove superuser() checks from pgstattuple
Previous Message Craig Ringer 2016-09-05 01:05:12 Re: [PATCH] COPY vs \copy HINT