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 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 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 considering I have already done a >VACUUM ANALYSE, I would not need to do it again ! ;-) ... or >am I missing something ? > >I could check the "don't give me experts advice" in the >preferences, but as I am quite a newbee in PG, I feel I need them ! ;-) > > >Cheers, >[EMAIL PROTECTED] >The Computing Froggy > > > > > > > > >_______________________________________________________________ >____________ >Découvrez une nouvelle façon d'obtenir des réponses à toutes >vos questions ! >Profitez des connaissances, des opinions et des expériences >des internautes sur Yahoo! Questions/Réponses >http://fr.answers.yahoo.com > >---------------------------(end of >broadcast)--------------------------- >TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so >that your > message can get through to the mailing list cleanly > ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
