This is a discussion on Re: "recovering prepared transaction" after serverrestart message within the pgsql Hackers forums, part of the PostgreSQL category; --> Added to TODO: * Improve logging of prepared statements recovered during startup http://archives.postgresql.org/pgsql...1/msg00092.php --------------------------------------------------------------------------- Joachim Wieland wrote: > There ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Added to TODO: * Improve logging of prepared statements recovered during startup http://archives.postgresql.org/pgsql...1/msg00092.php --------------------------------------------------------------------------- Joachim Wieland wrote: > There have been several reports that people could not vacuum any more or > observed strange locks even after server restart. The reason was that they > still had uncommitted prepared transactions around. > > > I wonder if it could help to change the log level from > > ereport(LOG, > (errmsg("recovering prepared transaction %u", xid))); > > to WARNING maybe in order to make that message more striking within the > normal startup messages. > > > > Joachim > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Have you searched our list archives? > > http://archives.postgresql.org -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |