I wrote:
> I tried it here. I don't get a crash; I get a rather long delay and
> then
> psql:vlad.sql:61: ERROR: Memory exhausted in AllocSetContextCreate(8192)
Some experimentation with other infinitely-recursive plpgsql functions
soon turned up a crash, however: spi.c was being sloppy about n
I tried it here. I don't get a crash; I get a rather long delay and
then
psql:vlad.sql:61: NOTICE: Error occurred while executing PL/pgSQL function
sp_loc_parent_check
psql:vlad.sql:61: NOTICE: line 12 at return
psql:vlad.sql:61: ERROR: Memory exhausted in AllocSetContextCreate(8192)
which
[EMAIL PROTECTED] writes:
> Trigger causes the server to crash with SEGV
> PostgreSQL version : PostgreSQL 7.2devel on i686-pc-linux-gnu, compiled by GCC
>egcs-2.91.66
You'll need to be more specific than "7.2devel". When was your last CVS
pull?
If it was since my trigger patches of yesterday
Vlad Seryakov ([EMAIL PROTECTED]) reports a bug with a severity of 1
The lower the number the more severe it is.
Short Description
Trigger causes the server to crash with SEGV
Long Description
PostgreSQL version : PostgreSQL 7.2devel on i686-pc-linux-gnu, compiled by GCC
egcs-2.91.66
create tab
[EMAIL PROTECTED] writes:
> Example form two pg_dump outputs
> 7.1.2 :
> COPY "list" FROM stdin;
> 7.0.2 :
> COPY "list" FROM stdin;
I have a very hard time considering that a bug...
regards, tom lane
---(end of broadcast)---
Jean-Francois Leveque ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
pg_dump: Too much in COPY ouput
Long Description
System: SuSE 7.0
select version(); :
PostgreSQL 7.1.2 on i686-pc-linux-gnu, compiled by GCC 2.95.2
pg_dump
