ERROR: cannot find attribute 1 of relation pg_temp.13465.1
От | Kristofer Munn |
---|---|
Тема | ERROR: cannot find attribute 1 of relation pg_temp.13465.1 |
Дата | |
Msg-id | Pine.LNX.4.04.10006161201360.14299-100000@munn.com обсуждение исходный текст |
Список | pgsql-hackers |
Greetings. I'm running into a recurring error on my system that has been running fine for quite a while. I dumped, dropped, created, rebuild and reloaded the database (all 2+ gigs) yesterday in the hopes of correcting whatever might be the problem. [PostgreSQL 6.5.3 on i686-pc-linux-gnu, compiled by gcc egcs-2.91.66] The following lines show up in my /var/log/messages... Jun 16 11:39:44 mymailman logger: ERROR: cannot find attribute 1 of relation pg_temp.13465.1 Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad file descriptor Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: FATAL 1: Socket command type Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: ERROR: unknown frontend message wasreceived Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: NOTICE: AbortTransaction and not inin-progress state Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: pq_recvbuf: recv() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: FATAL 1: Socket command type ? unknown Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: ERROR: unknown frontend message wasreceived Jun 16 11:39:44 mymailman logger: pq_flush: send() failed: Bad filedescriptor Jun 16 11:39:44 mymailman logger: NOTICE: AbortTransaction and not inin-progress state Etc etc. It goes off into an infinite recursion and then a script I have running detects that and shuts down and restarts postgres. Then the scripts that run restart themselves and everything's fine for a few more minutes and then we're back where we started from. I was waiting to upgrade to 7.0.2 for awhile to let it shake out before putting it on a production system. Thanks in advance for the consideration... - K Kristofer Munn * KMI * 732-254-9305 * AIM KrMunn * http://www.munn.com/
В списке pgsql-hackers по дате отправления: