From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: copy file from a client app to remote postgres isntance |
Date: | 2022-11-09 18:57:23 |
Message-ID: | f1881d8f-6bab-5366-be42-13e86bb8efcb@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/9/22 10:17, Peter J. Holzer wrote:
> On 2022-11-07 14:40:40 -0600, Ron wrote:
>> On 11/7/22 10:57, Вадим Самохин wrote:
>> I have an application that must copy a local file in csv format to a
>> postgres table on a remote host. The closest solution is this one (https://
>> stackoverflow.com/a/9327519/618020) It boils down to specifying a \copy
>> meta-command in a psql command:
>>
>> psql -U %s -p %s -d %s -f - <<EOT\n here hoes a \copy meta-command \nEOT\n
>>
>>
>> and executing it. But it's quite an unnatural way to write database code. Has anything changed in the last ten years? Or, is there a better way to copy file contents in a remote database?
>>
>>
>> I'd write a small Python script, using the csv module to read the data and
>> psycopg2 to load it.
> If you use insert statements it will be significantly slower (which may
> not matter for small files or one-off actions). If you use copy_from()
> you don't have to parse it (but then why use Python at all?)
If OP does not want to embed psql in his app, then he must find a different
solution. Python is such an option.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2022-11-09 19:22:10 | Re: "set role" semantics |
Previous Message | Bryn Llewellyn | 2022-11-09 18:55:35 | Re: "set role" semantics |