Re: pg_dump Crashes and core dumps

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Shibashish <shiba(at)it(dot)iitb(dot)ac(dot)in>
Cc: pgsql-bugs(at)postgresql(dot)org, pgman(at)candle(dot)pha(dot)pa(dot)us
Subject: Re: pg_dump Crashes and core dumps
Date: 2003-05-03 22:29:30
Message-ID: 16927.1052000970@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Shibashish <shiba(at)it(dot)iitb(dot)ac(dot)in> writes:
> When i do a "pg_dump test" it works fine.
> But When i do a "pg_dump working" I get "Segmentation fault (core dumped)"

Olivier Prenant just found a problem that could lead to pg_dump trouble
with any database using PL languages. Try the attached patch and see if
it fixes your problem.

regards, tom lane

*** src/bin/pg_dump/pg_dump.c.orig Thu Apr 24 22:28:22 2003
--- src/bin/pg_dump/pg_dump.c Sat May 3 18:09:51 2003
***************
*** 3591,3597 ****
resetPQExpBuffer(delqry);

/* Make a dependency to ensure function is dumped first */
! deps = malloc(sizeof(char *) * (2 + (strcmp(lanvalidator, "0") != 0) ? 1 : 0));
depIdx = 0;

(*deps)[depIdx++] = strdup(lanplcallfoid);
--- 3591,3597 ----
resetPQExpBuffer(delqry);

/* Make a dependency to ensure function is dumped first */
! deps = malloc(sizeof(char *) * 10);
depIdx = 0;

(*deps)[depIdx++] = strdup(lanplcallfoid);

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Achilleus Mantzios 2003-05-05 12:27:41 Wrong index usage in 7.3.2
Previous Message Josh Berkus 2003-05-03 18:44:44 Re: Very bizarre bug with corrupted index