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

Re: SELECT COUNT(*)... returns 0 ROWS

From: "PostgreSQL" <postgres(at)coopelesca(dot)co(dot)cr>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: SELECT COUNT(*)... returns 0 ROWS
Date: 2003-10-31 21:59:21
Message-ID: WorldClient-F200310311559.AA59210216@coopelesca.co.cr (view raw or flat)
Thread:
Lists: pgsql-admin
Thank to all

I was in the WRONG database. Sorry, and thanks!


-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff <threshar(at)torgo(dot)978(dot)org>
Cc: "PostgreSQL" <postgres(at)coopelesca(dot)co(dot)cr>, pgsql-admin(at)postgresql(dot)org
Date: Fri, 31 Oct 2003 16:27:31 -0500
Subject: Re: [ADMIN] SELECT COUNT(*)... returns 0 ROWS

> Jeff <threshar(at)torgo(dot)978(dot)org> writes:
> > "PostgreSQL" <postgres(at)coopelesca(dot)co(dot)cr> wrote:
> >> Why the result us CERO? the table have 1.400.000 rows!
> 
> > 1. did you remember to load data?
> > 2. did someone accidentally delete the data?
> > 3. are you connected to the correct db (I've panic'd before but
> realized
> > I was on dev, not production!)?
> > 4. sure that is the right table?
> 
> I'm wondering about MVCC-related conditions, which adds a couple
> more questions:
> 
> 5. Did you actually commit the transaction that loaded the rows?
> 6. Are you doing the SELECT COUNT(*) in a transaction that started
>    before the data-loading transaction committed?
> 
> 			regards, tom lane
> 
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo(at)postgresql(dot)org


In response to

pgsql-admin by date

Next:From: Jamie LawrenceDate: 2003-10-31 22:28:31
Subject: Security, proxies, etc. (was: Re: performance problem - 10.000 databases)
Previous:From: Tom LaneDate: 2003-10-31 21:27:31
Subject: Re: SELECT COUNT(*)... returns 0 ROWS

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