Re: transaction-wraparound data loss
От | Glenn Wiorek |
---|---|
Тема | Re: transaction-wraparound data loss |
Дата | |
Msg-id | 020a01c39a3e$d2270bd0$143264c8@jmlafferty.com обсуждение исходный текст |
Ответ на | transaction-wraparound data loss (Ari Jolma <Ari.Jolma@hut.fi>) |
Список | pgsql-admin |
See section 8.2.3 of the admin guide (v7.3) "Preventing transaction ID wraparound failures" ----- Original Message ----- From: "Ari Jolma" <Ari.Jolma@hut.fi> To: <pgsql-admin@postgresql.org> Sent: Friday, October 24, 2003 1:44 AM Subject: [ADMIN] transaction-wraparound data loss > Brian E. Pangburn asked some time ago about getting the warning > > WARNING: Some databases have not been vacuumed in over 2 billion transactions. > You may have already suffered transaction-wraparound data loss. > > while doing a routine vacuum. Tom Lane answered but did not have an > answer right away. > > I got the same message from my redhat installed > postgresql-server-7.3.2-3. I tried a vacuum after this message and did > not get any warnings. > > This is my pg_database. > > template1=# select * from pg_database; > datname | datdba | encoding | datistemplate | datallowconn | > datlastsysoid | datvacuumxid | datfrozenxid | datpath | datconfig | > datacl > -----------+--------+----------+---------------+--------------+----------- ----+--------------+--------------+---------+-----------+----------------- > clime | 100 | 0 | f | t | > 16974 | 3226 | 3221228699 | | | > template1 | 1 | 0 | t | t | > 16974 | 3449 | 3221228922 | | | {=,postgres=CT} > template0 | 1 | 0 | t | f | > 16974 | 427 | 427 | | | {=,postgres=CT} > (3 rows) > > Regards, > > Ari > > ** > > -- > Ari Jolma, Ari.Jolma@hut.fi, Professor of Geoinformatics > Cartography and Geoinformatics, Helsinki University of Technology > POBox 1200, 02015 TKK, Finland > http://www.hut.fi/Units/Cartography > > > > ---------------------------(end of broadcast)--------------------------- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > >
В списке pgsql-admin по дате отправления: