Re: pg_upgrade: out of memory - Mailing list pgsql-general

From Carrington, Matthew (Produban)
Subject Re: pg_upgrade: out of memory
Date
Msg-id 53E23B63FBFF3645A2CDD9BE5933C60C8B1194F0FA@ENTAAP2407P.an.ad.anplc.co.uk
Whole thread Raw
In response to pg_upgrade: out of memory  ("Carrington, Matthew (Produban)" <Matthew.Carrington@Produban.co.uk>)
Responses Re: pg_upgrade: out of memory  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Tom,

I traced through the problem with 'no symbol table' being created and managed to create a version of Postgres 9.2.1
witha symbol table. Here's the trace ... 

Rebuild postgres with debugging ...

export OBJECT_MODE=64
export CFLAGS="-maix64 -g"
export LDFLAGS="-maix64 -Wl,-bbigtoc"
export AR="ar -X64"
export "CC=/opt/freeware/bin/gcc -maix64"

./configure --enable-debug --prefix=/opt/serviceMonitoring/postgres_9.2.1 --disable-thread-safety --enable-cassert

make
cd contrib
make
cd ..
make install
cd contrib
make install

... get the backtrace ...

gdb "/opt/serviceMonitoring/postgres_9.2.1/bin/pg_dump"
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-ibm-aix5.1.0.0".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /ukmetmon/data/dataCollection/postgres_9.2.1/bin/pg_dump...done.
(gdb) b exit_horribly
Breakpoint 1 at 0x1002e3b4: file dumputils.c, line 1314.
(gdb) run --port 65432 --username "postgres" --verbose --schema-only --binary-upgrade -f dump.out template1
Starting program: /ukmetmon/data/dataCollection/postgres_9.2.1/bin/pg_dump --port 65432 --username "postgres" --verbose
--schema-only--binary-upgrade -f dump.out template1 
pg_dump: reading schemas
pg_dump: reading user-defined tables
pg_dump: reading extensions
pg_dump: reading user-defined functions
pg_dump: reading user-defined types
pg_dump: reading procedural languages
pg_dump: reading user-defined aggregate functions

Breakpoint 1, exit_horribly (modulename=0x0, fmt=0x10006a590 "out of memory\n")
    at dumputils.c:1314
1314    dumputils.c: A file or directory in the path name does not exist..
(gdb) bt
#0  exit_horribly (modulename=0x0, fmt=0x10006a590 "out of memory\n") at dumputils.c:1314
#1  0x000000010003247c in pg_malloc (size=0) at dumpmem.c:47
#2  0x0000000100008f54 in getAggregates (fout=0x11000bad0, numAggs=0xffffffffffff73c)
    at pg_dump.c:3614
#3  0x000000010002fcec in getSchemaData (fout=0x11000bad0, numTablesPtr=0xffffffffffff8a4)
    at common.c:145
#4  0x0000000100001370 in main (argc=11, argv=0xffffffffffff950) at pg_dump.c:683
(gdb) quit
A debugging session is active.

        Inferior 1 [process 483438] will be killed.

Quit anyway? (y or n) y

Hope that helps.

Matthew

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: 28 September 2012 16:27
To: Carrington, Matthew (Produban)
Subject: Re: [GENERAL] pg_upgrade: out of memory

"Carrington, Matthew (Produban)" <Matthew.Carrington@produban.co.uk> writes:
> ... presumably pg_extension is a 9.2 thing and I only have 9.0.1 installed.

I thought you were doing this test with 9.2?  Oh wait, this is 9.2
pg_dump against 9.0 server.  In that case leave off the EXISTS check:

SELECT tableoid, oid, proname AS aggname,
pronamespace AS aggnamespace,
pronargs, proargtypes,
(SELECT rolname FROM pg_catalog.pg_roles WHERE oid = proowner) AS rolname,
proacl AS aggacl
FROM pg_proc p
WHERE proisagg AND (
pronamespace !=
(SELECT oid FROM pg_namespace WHERE nspname = 'pg_catalog')
);

            regards, tom lane
Emails aren't always secure, and they may be intercepted or changed
after they've been sent. Produban doesn't accept liability if this
happens. If you think someone may have interfered with this email,
please get in touch with the sender another way. This message and any
documents attached to it do not create or change any contract unless
otherwise specifically stated. Any views or opinions contained in this
message are solely those of the author, and do not necessarily represent
those of Produban, unless otherwise specifically stated and the sender
is authorised to do so. Produban doesn't accept responsibility for
damage caused by any viruses contained in this email or its attachments.
Emails may be monitored. If you've received this email by mistake,
please let the sender know at once that it's gone to the wrong person
and then destroy it without copying, using, or telling anyone about its
contents. Produban Servicios Informaticos Generales, S.L. (UK Branch).
Registered office: Shenley Wood House, Chalkdell Drive, Shenley Wood,
Milton Keynes MK5 6LA. Branch registration number BR 008486.
Ref:[PDB#014]



pgsql-general by date:

Previous
From: Mr Dash Four
Date:
Subject: Re: strange permission error
Next
From: John R Pierce
Date:
Subject: Re: strange permission error