| 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 |
| Subject: | Re: SELECT COUNT(*)... returns 0 ROWS |
| Date: | 2003-10-31 21:27:31 |
| Message-ID: | 19924.1067635651@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PostgreSQL | 2003-10-31 21:59:21 | Re: SELECT COUNT(*)... returns 0 ROWS |
| Previous Message | Bruce Momjian | 2003-10-31 21:24:54 | Re: fishing out LOG: duration lines from the logfile. |