Re: Database not browsable during COPY on PostgreSQL - Mailing list pgsql-novice

From Majid Azimi
Subject Re: Database not browsable during COPY on PostgreSQL
Date
Msg-id CADOhCmsVa7CQx=qZ5LGWMg6yze3_7j9DLSDzbNbm=mvCbQMNow@mail.gmail.com
Whole thread Raw
In response to Database not browsable during COPY on PostgreSQL  (Majid Azimi <majid.merkava@gmail.com>)
Responses Re: Database not browsable during COPY on PostgreSQL  (Andreas Kretschmer <andreas@a-kretschmer.de>)
List pgsql-novice
On 3/6/12, Andreas Kretschmer <andreas@a-kretschmer.de> wrote:
>
>
>
> Majid Azimi <majid.merkava@gmail.com> hat am 6. März 2012 um 09:36
> geschrieben:
>
>> Hi guys,
>>
>> When using COPY to restore a CSV file, PostgreSQL shows alot of
>>
>> CONTEXT:  COPY tbl_vbvdata, line 8039085:
>> "1648469982,20431325,1314343300,4.5,87,1,643160,1"
>>
>> Also phppgadmin shows that the real database size(4GB) but when I
>> choose to browse the table it shows Estimated row count to 0. I did a
>> VACUUM ANALYZE. After that simple SELECT queries returns 0 rows, Also:
>>
>> SELECT count(*) FROM tbl_vbvdata
>>
>> return 0. Can anyone help?
>
>
> Your COPY is running inside a Transaction, PhpPgAdmin is outside, it can't
> see
> the not-commited rows.
>
>
> Andreas
>

I pressed CTRL+C when COPY was running and cancelled the process. Now
the DB size is still 4GB but no data is available for SELECT. How can
I commit that?

pgsql-novice by date:

Previous
From: Majid Azimi
Date:
Subject: Database not browsable during COPY on PostgreSQL
Next
From: Piyush Lenka
Date:
Subject: pg_dump : no tables were found.