POSTGRESQL BUG REPORT TEMPLATE
Your name : Edmund Bacon
Your email address : [EMAIL
POSTGRESQL BUG REPORT
Your name : Edmund Bacon
Your email address : ebacon (at
I am unable to get this patch to compile:
gcc version : gcc (GCC) 3.2 20020329 (experimental)
uname -srm : HP-UX B.11.22 ia64
tar xvf postgresql-7.3.4.tar
cd postgresql-7.3.4
patch -p0 ../PostgreSQL-7.3.4_hpux3_11iv2_IA-64.patch
./configure
[snip]
make
[snip]
gmake[4]: Entering directory
uoted string at or near "$$
LANGUAGE plpgsql;" at character 1
pg_restore: [archiver (db)] could not execute query: ERROR: function
public.foo() does not exist
--
-- PostgreSQL database dump complete
--
WARNING, errors ignored on restore: 3
$
Yep, but we still can't re
se dump complete
--
$
Tom Lane wrote:
Edmund Bacon <[EMAIL PROTECTED]> writes:
pg_dump/restore in 8.0beta1 are not working well with formats other
thans plain text:
What seems to be broken is --clean mode, because it drops and fails to
restore the public schema. I can see no reason that it
The following bug has been logged online:
Bug reference: 1440
Logged by: Edmund Bacon
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0
Operating system: Linux Redhat 9 Pentium-4
Description:ecpg seg faults
Details:
I have here a shortish source file that
: chunk is already free
If you have a core dump then maybe you can do a backtrace and see
where that's happening.
This assumes, perhaps prematurely, that the free() problem is causing
the core dump on your platform. In any case, a backtrace should
help track down the problem.
--
Edmun
0x400f7a67 in __libc_start_main () from /lib/i686/libc.so.6
Tom Lane wrote:
Edmund Bacon <[EMAIL PROTECTED]> writes:
According to the backtrace, it appears to be dieing in malloc.
That's consistent with the idea that the multiple free is the source of
trouble --- multiple free() co
