Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly - Mailing list pgsql-general

From Tod McQuillin
Subject Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly
Date
Msg-id Pine.GSO.4.31.0101091909530.333-100000@sysadmin
Whole thread Raw
In response to Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, 9 Jan 2001, Tom Lane wrote:

> -S suppresses all log output, so first you need to get rid of that.

The postgres.1 man page from postgresql-7.0.3/doc/man.tar.gz says:

       -S SortSize
              Specifies the amount of memory to be used by inter-
              nal  sorts and hashes before resorting to temporary
              disk files. The value is  specified  in  kilobytes,
              and defaults to 512 kilobytes. Note that for a com-
              plex query, several sorts and/or  hashes  might  be
              running  in  parallel, and each one will be allowed
              to use as much  as  SortSize  kilobytes  before  it
              starts to put data into temporary files.

Who is right?
--
Tod McQuillin



pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: "Cluster" means "tangle" for me
Next
From: Tom Lane
Date:
Subject: Re: Re: COPY error: pqReadData() -- backend closed the channel unexpectedly