On Apr 24, 2013, at 6:14 AM, Bill Moran wrote:
>>>
>
> Write your own client that uses the copy interface to
> load a file from wherever and send it to the server.
>
> Or just use the one built in to psql, as Jasen suggested.
>
I am using "copy to" to write data from the db out to csv files.
> On 2013-04-23, Kirk Wythers wrote:
> > I would like to run the COPY command as a user other than "postgres". I
> > find it a bit of a pain (or at least requiring an extra step or two) to
> > have the postgres user own the files that I am creating with COPY TO. Here
> > is a simple example wh
On 2013-04-23, Kirk Wythers wrote:
> I would like to run the COPY command as a user other than "postgres". I find
> it a bit of a pain (or at least requiring an extra step or two) to have the
> postgres user own the files that I am creating with COPY TO. Here is a simple
> example where the loc
On Tue, Apr 23, 2013 at 1:11 PM, Kirk Wythers wrote:
> I would like to run the COPY command as a user other than "postgres". I find
> it a bit of a pain (or at least requiring an extra step or two) to have the
> postgres user own the files that I am creating with COPY TO. Here is a simple
> exa
On Tue, Apr 04/23/13, 2013 at 03:11:21PM -0500, Kirk Wythers wrote:
> I would like to run the COPY command as a user other than "postgres".
> I find it a bit of a pain (or at least requiring an extra step or two)
> to have the postgres user own the files that I am creating with COPY
> TO. Here is a
I would like to run the COPY command as a user other than "postgres". I find it
a bit of a pain (or at least requiring an extra step or two) to have the
postgres user own the files that I am creating with COPY TO. Here is a simple
example where the location '/some/path/to/file/file.csv' is owned
