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

From Andreas Kretschmer
Subject Re: Database not browsable during COPY on PostgreSQL
Date
Msg-id 317898473.129.1331024639054.JavaMail.open-xchange@ox.ims-firmen.de
Whole thread Raw
In response to Re: Database not browsable during COPY on PostgreSQL  (Majid Azimi <majid.merkava@gmail.com>)
List pgsql-novice


Majid Azimi <majid.merkava@gmail.com> hat am 6. März 2012 um 10:01 geschrieben:

> 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?


You can't, the whole transaction is canceled now.


Andreas

pgsql-novice by date:

Previous
From: Majid Azimi
Date:
Subject: Re: Database not browsable during COPY on PostgreSQL
Next
From: Michael Wood
Date:
Subject: Re: running COPY with remote DB and local file