On Wed, 31 Aug 2011, Craig Ringer wrote:
Yeah, or use the client/server copy protocol via psql's \copy command.
Craig,
I was aware there was a back-slash version but did not recall when its use
is appropriate nor just how to use it.
Thanks,
Rich
--
Sent via pgsql-general mailing list (pg
On 31/08/2011 1:34 AM, Rich Shepard wrote:
On Tue, 30 Aug 2011, Scott Mead wrote:
In this case, it's not about YOU and your permissions, it's about the
server. The COPY command writes data as the 'postgres' operating system
user (or whichever user owns the postgres backend process).
Scott,
A
On Tue, 30 Aug 2011, Rich Shepard wrote:
Ah so. User 'postgres' is in the same group ('users') as I am, so I need
to change the perms on the data directory to 775 to give postgres write
access.
That did the trick. Thanks for the lesson, Scott.
Rich
--
Sent via pgsql-general mailing list (
On Tue, 30 Aug 2011, Scott Mead wrote:
In this case, it's not about YOU and your permissions, it's about the
server. The COPY command writes data as the 'postgres' operating system
user (or whichever user owns the postgres backend process).
Scott,
Ah so. User 'postgres' is in the same group
On Tue, 30 Aug 2011, Scott Ribe wrote:
Where is the server and where are you? You are issuing a command to the
server to create a file at that path on the server.
It's sitting right here next to my desk. That host is the network server
and my workstation. Yes, my home directory (and all othe
On Tue, Aug 30, 2011 at 1:20 PM, Scott Ribe wrote:
> On Aug 30, 2011, at 11:14 AM, Rich Shepard wrote:
>
> > The permissions on that directory are 755 and it's owned by me. Since I
> > have no problems writing other files to that directory I must have the
> > command syntax incorrect but I don't s
On Aug 30, 2011, at 11:14 AM, Rich Shepard wrote:
> The permissions on that directory are 755 and it's owned by me. Since I
> have no problems writing other files to that directory I must have the
> command syntax incorrect but I don't see where.
Where is the server and where are you? You are iss
x <[EMAIL PROTECTED]> writes:
> pqReadData() -- backend closed the channel unexpectedly.
That shouldn't happen :-(. Look for a core file in $PGDATA/base/yourdb/core
(if you don't find one, you probably need to restart the postmaster with
"ulimit -c unlimited" to allow core dumps). Then do
x <[EMAIL PROTECTED]> writes:
> pqReadData() -- backend closed the channel unexpectedly.
> This probably means the backend terminated abnormally
> before or while processing the request.
> PQendcopy: resetting connection
>
> 3. I'm running the Windows/cygwin version of the psql
