Re: Database not browsable during COPY on PostgreSQL

From: Majid Azimi <majid(dot)merkava(at)gmail(dot)com>
To: Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>
Cc: pgsql-novice <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Database not browsable during COPY on PostgreSQL
Date: 2012-03-06 09:01:29
Message-ID: CADOhCmsVa7CQx=qZ5LGWMg6yze3_7j9DLSDzbNbm=mvCbQMNow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On 3/6/12, Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> wrote:
>
>
>
> Majid Azimi <majid(dot)merkava(at)gmail(dot)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?

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message Andreas Kretschmer 2012-03-06 09:03:58 Re: Database not browsable during COPY on PostgreSQL
Previous Message Andreas Kretschmer 2012-03-06 08:46:27 Re: Database not browsable during COPY on PostgreSQL