Re: select * and save into a text file failed - Mailing list pgsql-admin

From Lee Wu
Subject Re: select * and save into a text file failed
Date
Msg-id E1F0E4D89D8FA44789DFC065C8E755281A360D@mxlhq-exch01.corp.mxlogic.com
Whole thread Raw
In response to select * and save into a text file failed  ("Lee Wu" <Lwu@mxlogic.com>)
Responses Re: select * and save into a text file failed
Re: select * and save into a text file failed
List pgsql-admin

Even without saving to file, it is still killed:

 

Welcome to psql 8.0.3, the PostgreSQL interactive terminal.

 

Type:  \copyright for distribution terms

       \h for help with SQL commands

       \? for help with psql commands

       \g or terminate with semicolon to execute query

       \q to quit

 

My_db=# select * from a_table;

Killed

bash-2.05b$

 

PG log shows:

could not send data to client: Connection reset by peer

could not send data to client: Broken pipe

unexpected EOF on client connection

 

Can anyone help?

 

Thanks,

 

PS: psql launched from the same PG server box.


From: Lee Wu
Sent: Friday, June 10, 2005 9:25 AM
To: pgsql-admin@postgresql.org
Subject: select * and save into a text file failed

 

Hi,

 

When I try to save a query result into a text file from “select * from a_table”, once I got:

out of memory for query result

under psql

 

Once got killed:

My_db=# select * from a_table;

Killed

bash-2.05b$

 

And once it caused PG crashed.

 

My PG version is:

select version();

                                                 version

----------------------------------------------------------------------------------------------------------

 PostgreSQL 8.0.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2.3 20030502 (Red Hat Linux 3.2.3-49)

(1 row)

 

The table has 6287585 rows, and takes 2805000 bytes.

 

From the PG log, I can only find:

could not send data to client: Connection reset by peer

could not send data to client: Broken pipe

unexpected EOF on client connection

 

How can I save PG data into text file without using pg_dump?

 

Thanks,

 

PS: I know pg_dump, but it is not my option.

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: How to recover when can't start database
Next
From: "Bruno G. Albuquerque"
Date:
Subject: Re: Indexes getting corrupted.