Tom Lane wrote:
Gerhard Hintermayer [EMAIL PROTECTED] writes:
... x should be y
I do get these messages one 2 of my servers running mostly on identical
data. The servers are unix-based and are running 8.1.8 under linux (Gentoo).
Update.
I thought the fixed error was related to running
Gerhard Hintermayer wrote:
Tom Lane wrote:
Gerhard Hintermayer [EMAIL PROTECTED] writes:
... x should be y
I do get these messages one 2 of my servers running mostly on
identical data. The servers are unix-based and are running 8.1.8
under linux (Gentoo).
Update.
I thought the fixed error
... x should be y
I do get these messages one 2 of my servers running mostly on identical
data. The servers are unix-based and are running 8.1.8 under linux (Gentoo).
On one server the message appears only after vacuum-ing, on the other I
had some errors after inserting into the table too
On Mon, Jul 02, 2007 at 11:46:54AM +0200, Gerhard Hintermayer wrote:
... x should be y
I do get these messages one 2 of my servers running mostly on identical
data. The servers are unix-based and are running 8.1.8 under linux (Gentoo).
On one server the message appears only after
Gerhard Hintermayer [EMAIL PROTECTED] writes:
... x should be y
I do get these messages one 2 of my servers running mostly on identical
data. The servers are unix-based and are running 8.1.8 under linux (Gentoo).
Update.
http://developer.postgresql.org/pgdocs/postgres/release-8-1-9.html
Martijn van Oosterhout wrote:
On Mon, Jul 02, 2007 at 11:46:54AM +0200, Gerhard Hintermayer wrote:
... x should be y
I do get these messages one 2 of my servers running mostly on identical
data. The servers are unix-based and are running 8.1.8 under linux (Gentoo).
On one server the message
Tom Lane wrote:
Gerhard Hintermayer [EMAIL PROTECTED] writes:
... x should be y
I do get these messages one 2 of my servers running mostly on identical
data. The servers are unix-based and are running 8.1.8 under linux (Gentoo).
Update.
