Joris Dobbelsteen wrote:
> I have the feeling this could be caused by pgAdmin because it is caching
> information. Perhaps that a refresh of the database is a workarround.
>
> Unfortunally I'm no expert and I'm not sure about this.
You should refresh the table node following vacuum and check that the
estimated rows matches (or is close to) the counted rows. If they are
wildly different, then you need to vacuum (and pgAdmin will most likely
display the hint).
Regards Dave
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
