When the application starts i have put a code that checks if the lookup tables are empty. If they are empty I add predefined hard coded rows as follows:
clear(vrsta_transakcije)
VT:vrsta_transakcije='UP'
VT:opis='Primitak kuna sa računa za redovno poslovanje'
add(vrsta_transakcije)
This particular table has 27 predefined values. When I check the table with pgAdmin I get:
"Running VACUUM recommended.
The estimated row count significatly from the actual row count."
If I add just two rows then I get no message.
I have then tried to not add at init time 27 lookup values, but instead i add them manually through ABC generated form. The result is the same. VACUUM
However the application behaves well. It is just the pgAdmin that shows this error.
Since I have to certificate this software it would probably not pass the certificate process if they open the database with pgAdmin.
Can you help me with this?
Thanks
Nenad
P.S. The lookup table is
vrsta_transakcije FILE,DRIVER('ODBC'),OWNER('wmj'),NAME('vrsta_transakcije'),PRE(vt),CREATE,BINDABLE,THREAD
KeyVT KEY(vt:vrsta_transakcije),NOCASE,OPT,PRIMARY
Record RECORD,PRE()
vrsta_transakcije STRING(2)
opis STRING(200)
END
END
It has no relation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry again. When I have started this project one month ago i have downloaded the last postgre so my version is 9.1, while i see i use postgresql-8.4-701.jdbc4.jar.
Can this be the problem. How can i use different java jdbc provider for postgre. Should i change the runtime pom.xml and change the dependency 8.4-701.jdbc4, but to what?
thanks
Nenad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The issue you are finding with VACUUM recommendation is maintenance related. The immediate way to take care of this issue would be to run "vacuum analyze". You may want to configure PG to collect better statistics automatically. How you tweak the settings will depend on the version you're using. Configurations are stored in postgresql.conf, and changes may require restarting the database service to take effect.
I wouldn't expect a change in version of the jdbc driver to solve this issue as it's not an error, but a friendly notification.
-Joshua
Joshua Berry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, I will study the postgre configuration. I thought my application is inserting rows in wrong manner, so i had fear that in future i will disocover i have to tweak something in the code. Since I have to undergo the certificate process, after i hopefully pass it i can not change a dot in the code.
Nenad
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When the application starts i have put a code that checks if the lookup tables are empty. If they are empty I add predefined hard coded rows as follows:
clear(vrsta_transakcije)
VT:vrsta_transakcije='UP'
VT:opis='Primitak kuna sa računa za redovno poslovanje'
add(vrsta_transakcije)
This particular table has 27 predefined values. When I check the table with pgAdmin I get:
"Running VACUUM recommended.
The estimated row count significatly from the actual row count."
If I add just two rows then I get no message.
I have then tried to not add at init time 27 lookup values, but instead i add them manually through ABC generated form. The result is the same. VACUUM
However the application behaves well. It is just the pgAdmin that shows this error.
Since I have to certificate this software it would probably not pass the certificate process if they open the database with pgAdmin.
Can you help me with this?
Thanks
Nenad
P.S. The lookup table is
vrsta_transakcije FILE,DRIVER('ODBC'),OWNER('wmj'),NAME('vrsta_transakcije'),PRE(vt),CREATE,BINDABLE,THREAD
KeyVT KEY(vt:vrsta_transakcije),NOCASE,OPT,PRIMARY
Record RECORD,PRE()
vrsta_transakcije STRING(2)
opis STRING(200)
END
END
It has no relation.
I mean
"Running VACUUM recommended. The estimated row count DEVIATES significatly from the actual row count."
Sorry again. When I have started this project one month ago i have downloaded the last postgre so my version is 9.1, while i see i use postgresql-8.4-701.jdbc4.jar.
Can this be the problem. How can i use different java jdbc provider for postgre. Should i change the runtime pom.xml and change the dependency 8.4-701.jdbc4, but to what?
thanks
Nenad
Hi Nenad,
The issue you are finding with VACUUM recommendation is maintenance related. The immediate way to take care of this issue would be to run "vacuum analyze". You may want to configure PG to collect better statistics automatically. How you tweak the settings will depend on the version you're using. Configurations are stored in postgresql.conf, and changes may require restarting the database service to take effect.
I wouldn't expect a change in version of the jdbc driver to solve this issue as it's not an error, but a friendly notification.
-Joshua
Joshua Berry
Thanks, I will study the postgre configuration. I thought my application is inserting rows in wrong manner, so i had fear that in future i will disocover i have to tweak something in the code. Since I have to undergo the certificate process, after i hopefully pass it i can not change a dot in the code.
Nenad