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
EMAIL PROTECTED] On Behalf Of
>Laurent ROCHE
>Sent: donderdag 18 januari 2007 13:55
>To: pgadmin-support@postgresql.org
>Subject: [pgadmin-support] Vacuum nag !
>
>Hi,
>
>I am working on an import of databases, so I keep dropping and
>re-creating schemas, and then populatin
Hi,
I am working on an import of databases, so I keep dropping and re-creating
schemas, and then populating tables.
Even, if I do a VACUUM ANALYSE on the entire DB, PG Admin will prompt me to
perform a VACUUM when I use one of the tables populated.
Is this normal ?
I would have thought that con
