SEO

#1 (**permalink**) 04-17-2008, 07:46 PM

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,
L@u
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 majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

#2 (**permalink**) 04-17-2008, 07:46 PM

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: pgadmin-support-owner@postgresql.org
>[mailto

gadmin-support-owner@postgresql.org] 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,
>L@u
>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 majordomo@postgresql.org so
>that your
> message can get through to the mailing list cleanly
>

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

#3 (**permalink**) 04-17-2008, 07:46 PM

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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode