Skip site navigation (1) Skip section navigation (2)

Re: Database not browsable during COPY on PostgreSQL

From: Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>
To: Majid Azimi <majid(dot)merkava(at)gmail(dot)com>, pgsql-novice <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Database not browsable during COPY on PostgreSQL
Date: 2012-03-06 08:46:27
Message-ID: 2108501990.85.1331023587092.JavaMail.open-xchange@ox.ims-firmen.de (view raw or flat)
Thread:
Lists: pgsql-novice


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

In response to

Responses

pgsql-novice by date

Next:From: Majid AzimiDate: 2012-03-06 09:01:29
Subject: Re: Database not browsable during COPY on PostgreSQL
Previous:From: Majid AzimiDate: 2012-03-06 08:36:00
Subject: Database not browsable during COPY on PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group