Thread: BUG #10726: database gets to an older backup out of nowhere!!!

BUG #10726: database gets to an older backup out of nowhere!!!

From
wildfox81@hotmail.com
Date:
The following bug has been logged on the website:

Bug reference:      10726
Logged by:          Walid
Email address:      wildfox81@hotmail.com
PostgreSQL version: 9.1.12
Operating system:   Win 7
Description:


Dear All, I have a PostgreSQL 9.1 server working with a java 6 application
on windows 7. Sometimes I found that the db travels in time and many records
are missing. It's like the DB had been restored to an older backup. Because
some of these fields are according to its cascading structure is
un-delete-able. Even the auto IDs goes back as if some one truncated the
table and restore just that amount of data.

Even I turned off the auto vacuum, I do vacuum the db on regular bases. The
problem used to appear more often when I used the auto vacuum.
Please also note that:

- Once the data came back to the DB after around 20 hours, interesting, ha!
- Once the PostgreSQL log recorded a restore commands outs of no where. I
saw in the log when the DB was dropped, recreated, then data started to be
imported.

Any ideas, suggestions, similar accidents!!!

Re: BUG #10726: database gets to an older backup out of nowhere!!!

From
"Tomas Vondra"
Date:
On 22 Červen 2014, 14:37, wildfox81@hotmail.com wrote:
> The following bug has been logged on the website:
>
> Bug reference:      10726
> Logged by:          Walid
> Email address:      wildfox81@hotmail.com
> PostgreSQL version: 9.1.12
> Operating system:   Win 7
> Description:
>
>
> Dear All, I have a PostgreSQL 9.1 server working with a java 6 application
> on windows 7. Sometimes I found that the db travels in time and many
> records
> are missing. It's like the DB had been restored to an older backup.
> Because
> some of these fields are according to its cascading structure is
> un-delete-able. Even the auto IDs goes back as if some one truncated the
> table and restore just that amount of data.
>
> Even I turned off the auto vacuum, I do vacuum the db on regular bases.
> The
> problem used to appear more often when I used the auto vacuum.
> Please also note that:
>
> - Once the data came back to the DB after around 20 hours, interesting,
> ha!
> - Once the PostgreSQL log recorded a restore commands outs of no where. I
> saw in the log when the DB was dropped, recreated, then data started to be
> imported.
>
> Any ideas, suggestions, similar accidents!!!

There's no built-in job that does dropdb/createdb/restore, so this is
quite certainly a pilot error. I.e. there's something wrong in your backup
scripts or some other tool you use (so it's not a postgres bug and
pgsql-bugs is not the right place to discuss that).

regards
Tomas