Thread: BUG #4568: sporadic error doing COUNT(*) on empty table

BUG #4568: sporadic error doing COUNT(*) on empty table

From
"Sameer Mahajan"
Date:
The following bug has been logged online:

Bug reference:      4568
Logged by:          Sameer Mahajan
Email address:      sameer_mahajan@symantec.com
PostgreSQL version: 8.1.4-1.3
Operating system:   Suse Linux
Description:        sporadic error doing COUNT(*) on empty table
Details:

While performing COUNT(*) on an empty table via libpq APIs I am spradically
getting an error.

the error is returning 7 for PQresultStatus(res)

and 0 for PQntuples(res) where res is the PGresult returned by this count(*)
query on the empty table.

Re: BUG #4568: sporadic error doing COUNT(*) on empty table

From
"Gurjeet Singh"
Date:
This mail landed in my Spam box... with this message:

"Warning: This message may not be from whom it claims to be. Beware of
following any links in it or of providing the sender with any personal
information"

You might want to report it again.

Best regards

On Mon, Dec 8, 2008 at 6:34 PM, Sameer Mahajan
<sameer_mahajan@symantec.com>wrote:

>
> The following bug has been logged online:
>
> Bug reference:      4568
> Logged by:          Sameer Mahajan
> Email address:      sameer_mahajan@symantec.com
> PostgreSQL version: 8.1.4-1.3
> Operating system:   Suse Linux
> Description:        sporadic error doing COUNT(*) on empty table
> Details:
>
> While performing COUNT(*) on an empty table via libpq APIs I am spradically
> getting an error.
>
> the error is returning 7 for PQresultStatus(res)
>
> and 0 for PQntuples(res) where res is the PGresult returned by this
> count(*)
> query on the empty table.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs
>



--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com

EnterpriseDB      http://www.enterprisedb.com

Mail sent from my BlackLaptop device

Re: BUG #4568: sporadic error doing COUNT(*) on empty table

From
John R Pierce
Date:
Gurjeet Singh wrote:
> This mail landed in my Spam box... with this message:
>
> "Warning: This message may not be from whom it claims to be. Beware of
> following any links in it or of providing the sender with any personal
> information"

it must have been at your end, it arrived via the [bugs] list in my
inbox just fine.

Re: BUG #4568: sporadic error doing COUNT(*) on empty table

From
"Dave Page"
Date:
On Sun, Dec 14, 2008 at 6:00 PM, John R Pierce <pierce@hogranch.com> wrote:
> Gurjeet Singh wrote:
>>
>> This mail landed in my Spam box... with this message:
>>
>> "Warning: This message may not be from whom it claims to be. Beware of
>> following any links in it or of providing the sender with any personal
>> information"
>
> it must have been at your end, it arrived via the [bugs] list in my inbox
> just fine.

It happened for me too - I guess Gmail thought it was a phishing
attempt for some reason.



--
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com

Re: BUG #4568: sporadic error doing COUNT(*) on empty table

From
"Sameer Mahajan"
Date:
How do I follow up on such bugs (helping narrowing down the issue,
getting a fix etc.)?=20

This is the first time I am reporting a bug on this alias.

Thanks,
Sameer

-----Original Message-----
From: John R Pierce [mailto:pierce@hogranch.com]=20
Sent: Sunday, December 14, 2008 11:31 PM
To: Gurjeet Singh
Cc: Sameer Mahajan; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #4568: sporadic error doing COUNT(*) on empty
table

Gurjeet Singh wrote:
> This mail landed in my Spam box... with this message:
>
> "Warning: This message may not be from whom it claims to be. Beware of

> following any links in it or of providing the sender with any personal

> information"

it must have been at your end, it arrived via the [bugs] list in my=20
inbox just fine.

Re: BUG #4568: sporadic error doing COUNT(*) on empty table

From
Alvaro Herrera
Date:
Sameer Mahajan escribió:
> How do I follow up on such bugs (helping narrowing down the issue,
> getting a fix etc.)?

Reply via email just like you're doing, making sure pgsql-bugs is on Cc:

--
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.