Обсуждение: Crashing backend!

Поиск
Список
Период
Сортировка

Crashing backend!

От
jwieck@debis.com (Jan Wieck)
Дата:
Outch,

just got the following on the 6.4b2:

pgsql=> create table t1 (a int4, b date);
CREATE
pgsql=> insert into t1 values (1, 'now');
INSERT 18282 1
pgsql=> update t1 set b = NULL where a = 1;
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally before or while processing the request.
We have lost the connection to the backend, so further processing is impossible.  Terminating.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #

Re: [HACKERS] Crashing backend!

От
Tom Lane
Дата:
jwieck@debis.com (Jan Wieck) writes:
> just got the following on the 6.4b2:
> pgsql=> create table t1 (a int4, b date);
> CREATE
> pgsql=> insert into t1 values (1, 'now');
> INSERT 18282 1
> pgsql=> update t1 set b = NULL where a = 1;
> pqReadData() -- backend closed the channel unexpectedly.

FWIW, that sequence works fine for me here, using current CVS sources.
Perhaps it's platform-dependent?  (I'm on HPUX.)  Or maybe a bug fixed
since the 6.4b2 tarball?

            regards, tom lane

Re: [HACKERS] Crashing backend!

От
Bruce Momjian
Дата:
> Outch,
> 
> just got the following on the 6.4b2:
> 
> pgsql=> create table t1 (a int4, b date);
> CREATE
> pgsql=> insert into t1 values (1, 'now');
> INSERT 18282 1
> pgsql=> update t1 set b = NULL where a = 1;
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally before or while processing the request.
> We have lost the connection to the backend, so further processing is impossible.  Terminating.

Just tested it on BSDI.  Worked fine.

--  Bruce Momjian                        |  http://www.op.net/~candle maillist@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


Re: [HACKERS] Crashing backend!

От
"Billy G. Allie"
Дата:
Jan Wieck wrote:
> Outch,
> 
> just got the following on the 6.4b2:
> 
> pgsql=> create table t1 (a int4, b date);
> CREATE
> pgsql=> insert into t1 values (1, 'now');
> INSERT 18282 1
> pgsql=> update t1 set b = NULL where a = 1;
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally before or while processing the request.
> We have lost the connection to the backend, so further processing is impossible.  Terminating.

I just tested it on the UnixWare 7.x port and it worked fine.
-- 
____       | Billy G. Allie    | Domain....: Bill.Allie@mug.org
|  /|      | 7436 Hartwell     | Compuserve: 76337,2061
|-/-|----- | Dearborn, MI 48126| MSN.......: B_G_Allie@email.msn.com
|/  |LLIE  | (313) 582-1540    | 




Re: [HACKERS] Crashing backend!

От
jwieck@debis.com (Jan Wieck)
Дата:
>
> Outch,
>
> just got the following on the 6.4b2:
>
> pgsql=> create table t1 (a int4, b date);
> CREATE
> pgsql=> insert into t1 values (1, 'now');
> INSERT 18282 1
> pgsql=> update t1 set b = NULL where a = 1;
> pqReadData() -- backend closed the channel unexpectedly.
>         This probably means the backend terminated abnormally before or while processing the request.
> We have lost the connection to the backend, so further processing is impossible.  Terminating.

    Seems  something  is  spying  my email here on the system. As
    soon as you all reported that it works for  you  the  problem
    disappeared.

    Sorry for the panic.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #