7.1.2: Backend message type 0x44 when selecting from a table

Поиск
Список
Период
Сортировка
От Lincoln Yeoh
Тема 7.1.2: Backend message type 0x44 when selecting from a table
Дата
Msg-id 3.0.5.32.20011119100215.00a76750@192.228.128.13
обсуждение исходный текст
Ответ на Re: DBD::Pg BYTEA Character Escaping  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: 7.1.2: Backend message type 0x44 when selecting from a table  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
select version();
                               version
---------------------------------------------------------------------
 PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled by GCC egcs-2.91.66
(1 row)

(doh, I thought I was running 7.1.3!).

SELECT * from arch_ranks_arch4 ;
Backend message type 0x44 arrived while idle
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>

Trying to pg_dump the table gives me this:

<snipped>
1526    2001-11-18 07:22:15+08  0                       BLANK   0       0
    0       0
1414414664      4714-11--2147483624 BC  218103907

\.
ERROR:  MemoryContextAlloc: invalid request size 1163153238
PQendcopy: resetting connection
SQL query to dump the contents of Table 'arch_ranks_arch4' did not execute
correctly.  After we read all th
e table contents from the backend, PQendcopy() failed.  Explanation from
backend: 'ERROR:  MemoryContextAll
oc: invalid request size 1163153238
'.
The query was: 'COPY "arch_ranks_arch4" TO stdout;
'.

Another similar table is ok. I have vacuumed - no errors, but the problem
still remained.

These tables have had a lot of updates on them (24/7 every second or so).
Fortunately it's not critical: just test tables.

The type:
CREATE TABLE "arch_ranks_arch4" (
        "id" integer,
        "updated" timestamp with time zone,
        "valid" integer,
        "name" text,
        "specialty" text,
        "status" text,
        "ranking" integer,
        "power" integer,
        "land" integer,
        "forts" integer,
        "description" text
);

I've truncated the table and it runs ok now.

The server itself hasn't crashed - up for 69 days.

Is it a fixed bug?

Regards,
Link.



В списке pgsql-general по дате отправления:

Предыдущее
От: Stephan Szabo
Дата:
Сообщение: Re: Problem with type in rule
Следующее
От: Tom Lane
Дата:
Сообщение: Re: 7.1.2: Backend message type 0x44 when selecting from a table