Re: Backend message type 0x50 arrived while idle
От | Wynn, Robin |
---|---|
Тема | Re: Backend message type 0x50 arrived while idle |
Дата | |
Msg-id | 99407664A0A7D511AD9900508BB0FB0301D1B14F@XCGVA030 обсуждение исходный текст |
Ответ на | Backend message type 0x50 arrived while idle ("Wynn, Robin" <RWynn@northropgrumman.com>) |
Ответы |
Re: Backend message type 0x50 arrived while idle
Re: Backend message type 0x50 arrived while idle |
Список | pgsql-general |
I know... the problem is two-fold. One, I had to have that in writing so I could justify upgrading, and two, we release in a few days and can't really change the database until that's complete (requires too many changes to existing things). I was just hoping someone here would know what that message meant so I could either document it, or prove it's not the database that's got a problem, it's our interaction with it. I've seen a number of people ask this question on a number of different versions of PostgreSQL (I believe the latest I've seen is 7.1.x), so I suspect that it's something we're doing... I just need to know what that message means, so I know how to troubleshoot it on our end. It's not incredibly descriptive :^P Robin -----Original Message----- From: scott.marlowe [mailto:scott.marlowe@ihs.com] Sent: Tuesday, December 03, 2002 3:35 PM To: Wynn, Robin Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] Backend message type 0x50 arrived while idle On Tue, 3 Dec 2002, Wynn, Robin wrote: > Hi... > > We're using an older version of PostgreSQL (6.5.1, to be precise), and we're > running into a problem where during certain inserts and queries we receive a > message "Backend message type 0x50 arrived while idle". We've also seen > backend message 0x45. Are these defined somewhere? We're trying to figure > out why this is happening, and if upgrading to a newer version of PostgreSQL > might fix the problem, and I'm not finding much in the way of documentation > that gets into the meaning of the various backend messages. Any > information you can give me would be appreciated, because this is getting > really frustrating. Thanks. I'm not sure what those messages mean, but 6.5.x is VERY old. Upgrading is worth it in so many ways, that even if it didn't fix this it would be worth it. Most likely this will be fixed by upgrading, but it's not likely you'll get a lot of help on troubleshooting a version that old. Since the release 6.5.x, 7.0.x, 7.1.x, 7.2.x and now 7.3 have come out. For one thing, 7.3 is literally about 100 times faster than 6.5.x, and it's definitely more reliable and has a lot fewer bugs in it.
В списке pgsql-general по дате отправления: