"Martial Braem" <Martial.Braem@xxxxxxxxx> writes: > Recently I observed a strange phenomenon: > 1) The database has some tables where I store my application data. > I have an additional table, with no relation to any other table, just > for logging purposes. In the database, a sequence is defined too. > 2) On day one, I store data in my application data tables and in > the logging table (transactional data). At the end of the day, I extract > the data from the database for daily reporting (the ultimate proof that > the transactions are actually committed). No problem there > 3) On day two, three, four and five, similar actions are taken > 4) On day six, there's no trace of any data from day two to day > five, except that the sequence, used in the application has not been > reset. Except for the sequence, it looks like the database was reverted > to the state of day one. > Does this sound absurd or is this in any way possible? I'd look around for a cron job or some other periodic task that thinks it's supposed to reload the database or something like that. Postgres doesn't forget stuff that easily ... unless it's told to. regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
