On 27 Gen, 06:31, [EMAIL PROTECTED] (Martijn van Oosterhout) wrote:
To repeat: If you think this may have happened DO NOT run vacuum
now.Actually, for XID wraparound a VACUUM may actually be the right thing.
I looked at this (with guidence from Tom) and we came to the conclusion
that XID
Hi everyone,
I have a problem with one of my costomers.
I made a program that uses a PostgreSQL (win32) database to save its data.
My customer claims that he lost lots of data reguarding his own clients
and that those data had surely been saved on the database.
My first guess is that he is the
BluDes wrote:
I made a program that uses a PostgreSQL (win32) database to save its data.
What version of PostgreSQL is this?
My customer claims that he lost lots of data reguarding his own clients
and that those data had surely been saved on the database.
My first guess is that he is the one
If data are deleted then they are still stored in database until VACUUM
cleans them. You can look by some hex viewer, if you see some know text
data there. Or I think there is also some tool which dump tuple list
from pages.
You can also see deleted data if you change current transaction ID.
On Jan 26, 2007, at 2:22 AM, BluDes wrote:
I have a problem with one of my costomers.
I made a program that uses a PostgreSQL (win32) database to save
its data.
My customer claims that he lost lots of data reguarding his own
clients and that those data had surely been saved on the
BluDes wrote:
Hi everyone,
I have a problem with one of my costomers.
I made a program that uses a PostgreSQL (win32) database to save its
data.
My customer claims that he lost lots of data reguarding his own
clients and that those data had surely been saved on the database.
My first guess is
BluDes [EMAIL PROTECTED] writes:
My customer claims that he lost lots of data reguarding his own clients and
that those data had surely been saved on the database.
Has this Postgres database been running for a long time? There is a regular
job called VACUUM that has to be run on every table