Re: PGAdmin3 and inherited tables

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: <pgadmin-support(at)postgresql(dot)org>
Subject: Re: PGAdmin3 and inherited tables
Date: 2006-10-20 16:10:56
Message-ID: C15EB3A0.17337%dpage@vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

I've committed this fix - thanks.

Regards, Dave.

On 20/10/06 10:49, "Markus Schaber" <schabi(at)logix-tt(dot)com> wrote:

> Hi,
>
> I have the same problem than described at
> http://www.pgadmin.org/archives/pgadmin-support/2006-04/msg00056.php but
> it was not resolved then, not even correctly understood, it seems.
>
> pgAdmin keeps telling me that I should VACUUM the base table that
> _really_ has 0 rows:
>
> stingray:navteq=# SELECT count(*) FROM ONLY test_phonetic.match;
> count
> -------
> 0
> (1 row)
>
> The problem is that pgAdmin seems to include the derived tables into
> their count query, and then complain that the estimate is off:
>
> stingray:navteq=# SELECT count(*) FROM test_phonetic.match;
> count
> ----------
> 71319833
> (1 row)
>
> So the correct fix would be to include the "ONLY" keyword when pgadmin3
> fetches the row count, IMHO this change should not break anything else.
>
> My version of pgAdmin3 is debianized 1.4.3-1.
>
> HTH,
> Markus
>

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Dave Page 2006-10-22 19:43:12 pgAdmin beta fixes
Previous Message kenp 2006-10-20 14:56:37 Set up Slony on Windows