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 th
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.
- Joris
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Beh
