when issuing a "VACUUM ANALYZE {tablename}", the
currently transaction wrap id is put into the logfile.
2006-10-22 07:04:50 LOG: transaction ID wrap
limit is 2147484172, limited by database "postgres"2006-10-22 07:04:56
LOG: transaction ID wrap limit is 2147484172, limited by database
"p
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Actually, the 8.0.X libpq function would still report 70401 if connected
> to a 7.4.1 database,
That was exactly the reason why the docs were written like that. Using
two examples that are both from the same major release doesn't seem to
me to be an imp
David Begley wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2703
> Logged by: David Begley
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.1.5
> Operating system: n/a
> Description:Cosmetic documentation error
> Details:
>
> The r
Seth Gordon wrote:
>
> The following bug has been logged online:
>
> Bug reference: 2701
> Logged by: Seth Gordon
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 7.4.7
> Operating system: Linux (Debian stable)
> Description:PQserverVersion function missing
>
manoj wrote:
> how to start postgresql at startup
That is not a bug.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
