| From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: \g filename |
| Date: | 2018-01-24 20:42:11 |
| Message-ID: | 748c4316-b336-dac0-d18a-7274c613de6f@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 01/24/2018 01:38 PM, Adrian Klaver wrote:
> On 01/24/2018 12:30 PM, Rob Sargent wrote:
>> I just ran a query (select myfunction() \g bad/filename) which took
>> almost an hour and a half then told me “no such file or directory”
>> since I had scrogged the path. Could this path not be checked prior
>> to actual execution of the query?
>
> Maybe?:
>
>
> test_(aklaver)> \o pg_test/some_file.txt
> pg_test/some_file.txt: No such file or directory
Ah yes, place the onus squarely on the user :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julio Cesar Tenganan Daza | 2018-01-24 21:27:23 | Using Token (JWT) authentication mechanism in Postgres |
| Previous Message | Adrian Klaver | 2018-01-24 20:38:52 | Re: \g filename |