pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_dump error
40+ messages / 24 participants
[nested] [flat]
* pg_dump error
@ 2000-04-17 03:02 Joe Conway <jconway2@home.com>
0 siblings, 0 replies; 40+ messages in thread
From: Joe Conway @ 2000-04-17 03:02 UTC (permalink / raw)
To: pgsql-admin
Hello,
I am getting the following error when trying to use pg_dump:
*******************************************************************
pg_dump cymi > cymi.2000_04_16.dmp
FATAL 1: Memory exhausted in AllocSetAlloc()
PQendcopy: resetting connection
SQL query to dump the contents of Table 'cymi_det_arc_01' did not execute
correctly. After we read all the table contents from the backend,
PQendcopy() failed. Explanation from backend: 'FATAL 1: Memory exhausted
in AllocSetAlloc()
'.
The query was: 'COPY "cymi_det_arc_01" TO stdout;
*******************************************************************
The table it is failing on is about 77MB in size, about 1 million tuples.
The server is dual pentium pro 200, with 512 MB RAM. I'm running PostgreSQL
6.5.2 on RedHat Linux 6.1, 686 SMP kernel. The kernel was recompiled per
Oracle's optimization recommendations for the Linux version of 8i (shared
memory and semaphore parameters, I can list if anyone feels it is relevant).
I tried starting the postmaster with -B10000, -B25000, and -B not there
(i.e. using default buffers). Same error in all three cases.
Any help or suggestions would be appreciated.
Thanks,
Joe
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump ERROR .......
@ 2001-03-28 12:07 agichen@kimo.com
0 siblings, 0 replies; 40+ messages in thread
From: agichen@kimo.com @ 2001-03-28 12:07 UTC (permalink / raw)
To: pgsql-admin
Hello,gurus
I find that u reply a topic about "Backend sent D message without prior
T"
problem on usenet, I think u can help me.
I'm new in PostgreSQL, I need to dump a table to another one, so I issue
the
pg_dump command.
but after I execute pg_dump -adt member db1 > /tmp/member.sql
( member table about 180000 rows)
I got the error message "Backend sent D message without prior T"
my environment ( 7.0.2 on Compaq Alpha Tru64 Unix)
options are:
/usr/local/pgsql/bin/postmaster
-p 5432
-D /var/db/pgsql
-B 256
-b /usr/local/pgsql/bin/postgres
-i
-N 128
-S
before I launch pg_dump, I have about 120M free memory,
but after 2-3 seconds, I got :
Backend sent D message without prior T
Backend sent D message without prior T
Backend sent D message without prior T
Backend sent D message without prior T
Backend sent D message without prior T
Any Idea ??
Rgds,
Agi Chen
----- Posted via NewsOne.Net: Free (anonymous) Usenet News via the Web -----
http://newsone.net/ -- Free reading and anonymous posting to 60,000+ groups
NewsOne.Net prohibits users from posting spam. If this or other posts
made through NewsOne.Net violate posting guidelines, email abuse@newsone.net
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2002-02-25 21:32 Srinivasa Rao Chava <s.chava@wcom.com>
2002-02-25 22:42 ` Re: pg_dump error Stephan Szabo <sszabo@megazone23.bigpanda.com>
2002-02-25 23:12 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 40+ messages in thread
From: s.chava@wcom.com @ 2002-02-25 21:32 UTC (permalink / raw)
To: pgsql-admin
I have recently upgraded to postgresql 7.2.
When I try to take backup with pg_dump, one of the database is
generating
the following error.
pg_dump: query to obtain procedure name for trigger
"ins_extranet_cspm_bug" did not return exactly one result
I checked the for the trigger "ins_extranet_cspm_bug" from
pg_trigger system catalog table, it is retrieving just one error.
What is the cause of this error and how can I fix it. We are planning
to upgrade
database to postgresql7.2 from 7.1.3 in this week. But now I'm scared
to do it in production with this problem.
Thanks for any help
chava
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2002-02-25 21:32 pg_dump error Srinivasa Rao Chava <s.chava@wcom.com>
@ 2002-02-25 22:42 ` Stephan Szabo <sszabo@megazone23.bigpanda.com>
1 sibling, 0 replies; 40+ messages in thread
From: Stephan Szabo @ 2002-02-25 22:42 UTC (permalink / raw)
To: Srinivasa Rao Chava <s.chava@wcom.com>; +Cc: pgsql-admin
On 25 Feb 2002, Srinivasa Rao Chava wrote:
> I have recently upgraded to postgresql 7.2.
> When I try to take backup with pg_dump, one of the database is
> generating
> the following error.
>
> pg_dump: query to obtain procedure name for trigger
> "ins_extranet_cspm_bug" did not return exactly one result
>
> I checked the for the trigger "ins_extranet_cspm_bug" from
> pg_trigger system catalog table, it is retrieving just one error.
What does
select * from pg_proc where oid=<tgfoid column of the trigger>;
give you?
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2002-02-25 21:32 pg_dump error Srinivasa Rao Chava <s.chava@wcom.com>
@ 2002-02-25 23:12 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 40+ messages in thread
From: Tom Lane @ 2002-02-25 23:12 UTC (permalink / raw)
To: s.chava@wcom.com; +Cc: pgsql-admin
s.chava@wcom.com (Srinivasa Rao Chava) writes:
> pg_dump: query to obtain procedure name for trigger
> "ins_extranet_cspm_bug" did not return exactly one result
The most likely bet is that there's no function at all that matches the
OID stored in the trigger. Have you done any deletion/recreation of
functions in the new database?
The error message that 7.2's pg_dump emits here seems less helpful than
the old one :-(. Will see if I can tweak it.
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2002-10-01 15:52 Ferdinand Smit <ferdinand@telegraafnet.nl>
2002-10-01 17:10 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 40+ messages in thread
From: Ferdinand Smit @ 2002-10-01 15:52 UTC (permalink / raw)
To: pgsql-admin
Hi,
What does this mean ?!? Is this a corrupt database, a bug or has the pg_dump
not enough memory ?
And ... how can i solve this problem ?
$ pg_dump login | gzip > login.dump.gz
pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293
pg_dump: lost synchronization with server, resetting connection
pg_dump: SQL command to dump the contents of table "postcodereeks" failed:
PQendcopy() failed.
pg_dump: Error message from server: pg_dump: The command was: COPY
"postcodereeks" TO stdout;
$ psql -c 'COPY "postcodereeks" TO stdout;' login > /tmp/postcodereeks
ERROR: MemoryContextAlloc: invalid request size 4294967293
lost synchronization with server, resetting connection
Config:
Machine; dual PIII with 1 Gb memory
DB version: PG 7.2.1
postgres.conf:
<zip>
shared_buffers = 2048
sort_mem = 1024
<zip>
Regards,
Ferdinand
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2002-10-01 15:52 pg_dump error Ferdinand Smit <ferdinand@telegraafnet.nl>
@ 2002-10-01 17:10 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 40+ messages in thread
From: Tom Lane @ 2002-10-01 17:10 UTC (permalink / raw)
To: Ferdinand Smit <ferdinand@telegraafnet.nl>; +Cc: pgsql-admin
Ferdinand Smit <ferdinand@telegraafnet.nl> writes:
> What does this mean ?!? Is this a corrupt database, a bug or has the pg_dump
> not enough memory ?
> $ pg_dump login | gzip > login.dump.gz
> pg_dump: ERROR: MemoryContextAlloc: invalid request size 4294967293
> pg_dump: lost synchronization with server, resetting connection
> pg_dump: SQL command to dump the contents of table "postcodereeks" failed:
> PQendcopy() failed.
First guess is a corrupted data value in table postcodereeks. Possibly
you can narrow down which row(s) have bad data and remove 'em.
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2003-11-06 17:35 David C. Brown <dbrown@centennialwines.com>
2003-11-06 18:20 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
2003-11-06 18:23 ` Re: pg_dump error David C. Brown <dbrown@centennialwines.com>
0 siblings, 2 replies; 40+ messages in thread
From: David C. Brown @ 2003-11-06 17:35 UTC (permalink / raw)
To: pgsql-admin
I'm receiving an error from pg_dumpall while trying to backup my
database. To explain, this database used to be 7.2.1 but we have
upgraded the server and I just used pg_dumpall and then reloaded that
data into the new system which runs on 7.3.3 The problem is I get an
error when using pg_dumpall/pg_dump.
Here are the version info and the error messages.
Old database.
version
-------------------------------------------------------------
PostgreSQL 7.2.1 on i586-pc-linux-gnu, compiled by GCC 2.96
(1 row)
New database.
version
---------------------------------------------------------------------------------------------------------
PostgreSQL 7.3.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2
20020903 (Red Hat Linux 8.0 3.2-7)
(1 row)
Error message when using pg_dump. I get the same message with pg_dumpall.
pg_dump -i -U postgres whse > db.out
Password:
pg_dump: server version: PostgreSQL 7.3.3 on i686-pc-linux-gnu, compiled
by GCC gcc (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7); pg_dump
version: 7.2.2
pg_dump: proceeding despite version mismatch
pg_dump: query to obtain list of data types failed: ERROR: Attribute
"typprtlen" not found
It says that it's using pg_dump version 7.2.2. I'm not sure if that is
the version that comes with 7.3.3, but PostgreSQL was compile fresh from
source on the new machine. Where it got this version of
pg_dump/pg_dumpall I'm unclear of.
If anyone has any ideas that could help me out it would be greatly
appreciated. I tried searching the pgsql-admin archives, but was unable
to find related items.
Thanks,
Dave
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2003-11-06 17:35 pg_dump error David C. Brown <dbrown@centennialwines.com>
@ 2003-11-06 18:20 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 40+ messages in thread
From: Tom Lane @ 2003-11-06 18:20 UTC (permalink / raw)
To: David C. Brown <dbrown@centennialwines.com>; +Cc: pgsql-admin
"David C. Brown" <dbrown@centennialwines.com> writes:
> It says that it's using pg_dump version 7.2.2. I'm not sure if that is
> the version that comes with 7.3.3, but PostgreSQL was compile fresh from
> source on the new machine. Where it got this version of
> pg_dump/pg_dumpall I'm unclear of.
Your PATH is set up to find the 7.2 executables (in particular pg_dump)
before, or instead of, the ones installed for 7.3. You need to fix the
PATH setting to find the 7.3 versions.
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2003-11-06 17:35 pg_dump error David C. Brown <dbrown@centennialwines.com>
@ 2003-11-06 18:23 ` David C. Brown <dbrown@centennialwines.com>
1 sibling, 0 replies; 40+ messages in thread
From: David C. Brown @ 2003-11-06 18:23 UTC (permalink / raw)
To: pgsql-admin
86 this request. I've found my problem. It seems that Dell had an old
version (7.2.2) of PostgreSQL installed. It was using pg_dump from that
version instead of the new version.
The database dump worked great with the new version.
Dave
David C. Brown wrote:
> I'm receiving an error from pg_dumpall while trying to backup my
> database. To explain, this database used to be 7.2.1 but we have
> upgraded the server and I just used pg_dumpall and then reloaded that
> data into the new system which runs on 7.3.3 The problem is I get an
> error when using pg_dumpall/pg_dump.
>
> Here are the version info and the error messages.
>
> Old database.
>
> version
> -------------------------------------------------------------
> PostgreSQL 7.2.1 on i586-pc-linux-gnu, compiled by GCC 2.96
> (1 row)
>
>
> New database.
>
>
> version
> ---------------------------------------------------------------------------------------------------------
>
> PostgreSQL 7.3.3 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.2
> 20020903 (Red Hat Linux 8.0 3.2-7)
> (1 row)
>
>
> Error message when using pg_dump. I get the same message with
> pg_dumpall.
>
> pg_dump -i -U postgres whse > db.out
> Password:
> pg_dump: server version: PostgreSQL 7.3.3 on i686-pc-linux-gnu,
> compiled by GCC gcc (GCC) 3.2 20020903 (Red Hat Linux 8.0 3.2-7);
> pg_dump version: 7.2.2
> pg_dump: proceeding despite version mismatch
> pg_dump: query to obtain list of data types failed: ERROR: Attribute
> "typprtlen" not found
>
> It says that it's using pg_dump version 7.2.2. I'm not sure if that
> is the version that comes with 7.3.3, but PostgreSQL was compile fresh
> from source on the new machine. Where it got this version of
> pg_dump/pg_dumpall I'm unclear of.
>
>
> If anyone has any ideas that could help me out it would be greatly
> appreciated. I tried searching the pgsql-admin archives, but was
> unable to find related items.
>
> Thanks,
> Dave
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump Error
@ 2004-06-29 09:38 Nigel Bishop <Nigel.Bishop@ioko.com>
2004-06-29 11:27 ` Re: pg_dump Error Guido Barosio <gbarosio@sinectis.com.ar>
2004-06-29 14:16 ` Re: pg_dump Error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 40+ messages in thread
From: Nigel Bishop @ 2004-06-29 09:38 UTC (permalink / raw)
To: pgsql-admin
Hi
I'm getting an error with pg_dump:
I'm using
pg_dump -v -C -U username database > ./dumpfile.dmp
and it errors with:
pg_dump: saving database definition
pg_dump: reading namespaces
pg_dump: reading user-defined types
pg_dump: reading user-defined functions
pg_dump: reading user-defined aggregate functions
pg_dump: reading user-defined operators
pg_dump: reading user-defined operator classes
pg_dump: reading user-defined tables
pg_dump: Attempt to lock table "Foo" failed. ERROR: MySchema:
permission denied
pg_dump: *** aborted because of error
Issueing a SELECT * FROM PG_TABLES;
Shows:
MySchema | Foo | postgres | t | f | f
If I try to drop this it errors saying the table foo doesn't exist.
Where did this object come from and how can I resolve the pg_dump error
TIA
Nigel
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump Error
2004-06-29 09:38 pg_dump Error Nigel Bishop <Nigel.Bishop@ioko.com>
@ 2004-06-29 11:27 ` Guido Barosio <gbarosio@sinectis.com.ar>
1 sibling, 0 replies; 40+ messages in thread
From: Guido Barosio @ 2004-06-29 11:27 UTC (permalink / raw)
To: ; +Cc: pgsql-admin
An idea only.
Ever try this?
select reltype from pg_class where relname='foo';
Then, delete the reltype from pg_class
To me goes fine.
Best wishes,
Guido
Nigel Bishop wrote:
>Hi
>
>I'm getting an error with pg_dump:
>
>I'm using
>
>pg_dump -v -C -U username database > ./dumpfile.dmp
>
>and it errors with:
>
>pg_dump: saving database definition
>pg_dump: reading namespaces
>pg_dump: reading user-defined types
>pg_dump: reading user-defined functions
>pg_dump: reading user-defined aggregate functions
>pg_dump: reading user-defined operators
>pg_dump: reading user-defined operator classes
>pg_dump: reading user-defined tables
>pg_dump: Attempt to lock table "Foo" failed. ERROR: MySchema:
>permission denied
>pg_dump: *** aborted because of error
>
>
>Issueing a SELECT * FROM PG_TABLES;
>
>Shows:
>
>MySchema | Foo | postgres | t | f | f
>
>
>If I try to drop this it errors saying the table foo doesn't exist.
>
>Where did this object come from and how can I resolve the pg_dump error
>
>
>TIA
>
>
>Nigel
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>
>
>
>
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump Error
2004-06-29 09:38 pg_dump Error Nigel Bishop <Nigel.Bishop@ioko.com>
@ 2004-06-29 14:16 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 40+ messages in thread
From: Tom Lane @ 2004-06-29 14:16 UTC (permalink / raw)
To: Nigel Bishop <Nigel.Bishop@ioko.com>; +Cc: pgsql-admin
"Nigel Bishop" <Nigel.Bishop@ioko.com> writes:
> pg_dump: Attempt to lock table "Foo" failed. ERROR: MySchema:
> permission denied
Looks like you need to grant yourself usage rights on the schema
"MySchema".
> If I try to drop this it errors saying the table foo doesn't exist.
Can't tell whether you forgot to schema-qualify the name or whether
you forgot to quote it to protect the mixed case, but something
along the lines of
drop table "MySchema"."Foo";
is what you would need. Note that that will also fail unless you've
fixed the permissions problem for MySchema, though.
> Where did this object come from
Presumably, you created it.
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2005-09-07 09:50 Adam Witney <awitney@sgul.ac.uk>
2005-09-07 14:54 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 14:55 ` Re: pg_dump error Michael Fuhr <mike@fuhr.org>
0 siblings, 2 replies; 40+ messages in thread
From: Adam Witney @ 2005-09-07 09:50 UTC (permalink / raw)
To: pgsql-admin
Hi,
I just ran into an error from pg_dump:
/usr/local/pgsql/bin/pg_dump -F p my_db
pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
144391872
pg_dump: SQL command to dump the contents of table "measured_bioassay_base"
failed: PQendcopy() failed.
pg_dump: Error message from server: ERROR: unexpected chunk number 3292
(expected 5) for toast value 144391872
pg_dump: The command was: COPY public.measured_bioassay_base (bioassay_id,
name, owner_id, writer_id, readers_id, is_deleted, delete_time, expt_id,
protocol_application_id, source_bioassay_id, filename, fileheader, format,
date_uploaded) TO stdout;
Any ideas whats happened here? It looks like one of my tables hasn't backed
up correctly. This table has a text field which contains large amounts of
data per field. The dump file is much smaller than last nights dump.
(PostgreSQL 7.4.8 on i686-pc-linux-gnu, compiled by GCC 2.95.4)
Thanks for any help
Adam
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2005-09-07 09:50 pg_dump error Adam Witney <awitney@sgul.ac.uk>
@ 2005-09-07 14:54 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:08 ` Re: pg_dump error Adam Witney <awitney@sgul.ac.uk>
1 sibling, 1 reply; 40+ messages in thread
From: Tom Lane @ 2005-09-07 14:54 UTC (permalink / raw)
To: Adam Witney <awitney@sgul.ac.uk>; +Cc: pgsql-admin
Adam Witney <awitney@sgul.ac.uk> writes:
> pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
> 144391872
> pg_dump: SQL command to dump the contents of table "measured_bioassay_base"
> failed: PQendcopy() failed.
> Any ideas whats happened here?
If you're lucky, it's just a corrupted index on the toast table for
"measured_bioassay_base", in which case a REINDEX will fix it. You'll
need to look at the pg_class entry for "measured_bioassay_base" to find
out what the toast table's name is. Something like
regression=# select relname from pg_class where oid =
regression-# (select reltoastrelid from pg_class where relname = 'measured_bioa
ssay_base');
relname
-----------------
pg_toast_597768
(1 row)
regression=# reindex table pg_toast.pg_toast_597768;
REINDEX
I would be interested to see "pg_filedump -i -f" output for the toast
table's index before you blow it away, if you have time for that.
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2005-09-07 09:50 pg_dump error Adam Witney <awitney@sgul.ac.uk>
2005-09-07 14:54 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
@ 2005-09-07 15:08 ` Adam Witney <awitney@sgul.ac.uk>
2005-09-07 15:28 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 40+ messages in thread
From: Adam Witney @ 2005-09-07 15:08 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
> I would be interested to see "pg_filedump -i -f" output for the toast
> table's index before you blow it away, if you have time for that.
Yep I can run this.... Can't seem to locate pg_filedump though... Its not in
contrib... Anyone know where it is these days?
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2005-09-07 09:50 pg_dump error Adam Witney <awitney@sgul.ac.uk>
2005-09-07 14:54 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:08 ` Re: pg_dump error Adam Witney <awitney@sgul.ac.uk>
@ 2005-09-07 15:28 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:40 ` Re: pg_dump error Adam Witney <awitney@sgul.ac.uk>
0 siblings, 1 reply; 40+ messages in thread
From: Tom Lane @ 2005-09-07 15:28 UTC (permalink / raw)
To: Adam Witney <awitney@sgul.ac.uk>; +Cc: pgsql-admin
Adam Witney <awitney@sgul.ac.uk> writes:
>> I would be interested to see "pg_filedump -i -f" output for the toast
>> table's index before you blow it away, if you have time for that.
> Yep I can run this.... Can't seem to locate pg_filedump though... Its not in
> contrib... Anyone know where it is these days?
Same place it's been for awhile:
http://sources.redhat.com/rhdb/
Be sure to grab the version that matches your PG version.
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2005-09-07 09:50 pg_dump error Adam Witney <awitney@sgul.ac.uk>
2005-09-07 14:54 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:08 ` Re: pg_dump error Adam Witney <awitney@sgul.ac.uk>
2005-09-07 15:28 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
@ 2005-09-07 15:40 ` Adam Witney <awitney@sgul.ac.uk>
2005-09-07 15:56 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 40+ messages in thread
From: Adam Witney @ 2005-09-07 15:40 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
On 7/9/05 4:28 pm, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
> Adam Witney <awitney@sgul.ac.uk> writes:
>>> I would be interested to see "pg_filedump -i -f" output for the toast
>>> table's index before you blow it away, if you have time for that.
>
>> Yep I can run this.... Can't seem to locate pg_filedump though... Its not in
>> contrib... Anyone know where it is these days?
>
> Same place it's been for awhile:
> http://sources.redhat.com/rhdb/
Got that now.... Sorry but I am being dim... But where do I find the file to
dump.. You want the index on pg_toast_134401982 right?
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2005-09-07 09:50 pg_dump error Adam Witney <awitney@sgul.ac.uk>
2005-09-07 14:54 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:08 ` Re: pg_dump error Adam Witney <awitney@sgul.ac.uk>
2005-09-07 15:28 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:40 ` Re: pg_dump error Adam Witney <awitney@sgul.ac.uk>
@ 2005-09-07 15:56 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 40+ messages in thread
From: Tom Lane @ 2005-09-07 15:56 UTC (permalink / raw)
To: Adam Witney <awitney@sgul.ac.uk>; +Cc: pgsql-admin
Adam Witney <awitney@sgul.ac.uk> writes:
> Got that now.... Sorry but I am being dim... But where do I find the file to
> dump.. You want the index on pg_toast_134401982 right?
Right (if that's the toast table you identified for the problem table).
It's probably named pg_toast_134401982_index. Look at its pg_class
entry to find its relfilenode number, and find the OID of the database
from pg_database, and then the file should be
$PGDATA/base/DBOID/RELFILENODE. For more info see
http://www.postgresql.org/docs/8.0/static/storage.html
(which is for 8.0, but everything except the remarks about tablespaces
applies to 7.4).
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2005-09-07 09:50 pg_dump error Adam Witney <awitney@sgul.ac.uk>
@ 2005-09-07 14:55 ` Michael Fuhr <mike@fuhr.org>
1 sibling, 0 replies; 40+ messages in thread
From: Michael Fuhr @ 2005-09-07 14:55 UTC (permalink / raw)
To: Adam Witney <awitney@sgul.ac.uk>; +Cc: pgsql-admin
On Wed, Sep 07, 2005 at 10:50:44AM +0100, Adam Witney wrote:
> pg_dump: ERROR: unexpected chunk number 3292 (expected 5) for toast value
> 144391872
> pg_dump: SQL command to dump the contents of table "measured_bioassay_base"
You might have a corrupted TOAST table. Have you had any hardware
problems, database or system crashes, etc., lately? Do you see any
unusual messages in the database or system log files? What are the
results of the following queries?
SELECT reltoastrelid::regclass
FROM pg_class
WHERE relname = 'measured_bioassay_base';
(The following query refers to the above result as pg_toast.pg_toast_XXXXXX.)
SELECT xmin, xmax, chunk_seq, length(chunk_data)
FROM pg_toast.pg_toast_XXXXXX
WHERE chunk_id = 144391872;
--
Michael Fuhr
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2005-09-28 15:13 Jerry Cadet <jjrc71@hotmail.com>
0 siblings, 0 replies; 40+ messages in thread
From: Jerry Cadet @ 2005-09-28 15:13 UTC (permalink / raw)
To: pgsql-admin
Hello,
I am running Postgresql 8.0 on a win3K machine. I launched a backup using
the pgAdmin III utility. I chose the TAR option with BLOBs. I received the
following messages:
pg_dump: dumping content of table face
pg_dump: (tar archiver) actual file length (-760496003) does not match
expected (-760496003)
pg_dump: *** aborted because of error
Process returned exit code 1
My question would be: what is happenning with the face table which I just
vaccuumed and reindexed before I launched the backup? I have to say that
this table contain a blob field and is quite huge (5 million rows)
Thanks
^ permalink raw reply [nested|flat] 40+ messages in thread
* PG_DUMP Error
@ 2005-10-06 10:33 Cédric Buschini <cbuschini@carax.com>
0 siblings, 0 replies; 40+ messages in thread
From: Cédric Buschini @ 2005-10-06 10:33 UTC (permalink / raw)
To: pgsql-admin
Hi,
Doing " pg_dump -h192.168.XXX.XXX -U USER -d DB_NAME -C >
/file/where/dump/is/stored "
I got this error :
---------------------------------------------------------------------------------------
pg_dump: SQL command failed
pg_dump: Error message from server: server closed the connection
unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
pg_dump: The command was: FETCH 100 FROM _pg_dump_cursor
----------------------------------------------------------------------------------------
Thx
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2006-07-06 12:25 manjula hettiarachchi <manjula_55@yahoo.com>
2006-07-06 12:29 ` Re: pg_dump error Dilipkumar <dilipkumar_parikh@sifycorp.com>
0 siblings, 1 reply; 40+ messages in thread
From: manjula hettiarachchi @ 2006-07-06 12:25 UTC (permalink / raw)
To: pgsql-admin; postgresql-l <postgresql-l@groups.ittoolbox.com>
Hello List
I am using postgresql 7.4.7 in a voip production
setup.
I have been using pg_dump -Fc for regular backing up.
Since yesterday i am getting the following error for
the command:
root# pg_dump -h 'localhost' voipdb -t voipcall -Fc -f
voipcall.bak
The error is :
pg_dump: ERROR: invalid memory alloc request size
4294967293
pg_dump: SQL command to dump the contents of table
"voipcall" failed: PQendcopy() failed.
pg_dump: Error message from server: ERROR: invalid
memory alloc request size 4294967293
pg_dump: The command was: COPY public.voipcall (id,
accountid, .........., prefix) TO stdout;
However when i tried to Vacuum analyze the same table
its fine and no errors. Also the SQL access to the
same table runs fine without any errors.
Only the pg_dump is failing for this particular table.
Can anyone suggest a method to fix this?
Thanks in advance
Manjula
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2006-07-06 12:25 pg_dump error manjula hettiarachchi <manjula_55@yahoo.com>
@ 2006-07-06 12:29 ` Dilipkumar <dilipkumar_parikh@sifycorp.com>
2006-07-06 12:52 ` FWD: [ADMIN] pg_dump error Guido Barosio <gbarosio@gmail.com>
0 siblings, 1 reply; 40+ messages in thread
From: Dilipkumar @ 2006-07-06 12:29 UTC (permalink / raw)
To: manjula hettiarachchi <manjula_55@yahoo.com>; +Cc: pgsql-admin; postgresql-l <postgresql-l@groups.ittoolbox.com>
Hi,
If you are trying to take a table dump try using this
pd_dump databasename -t tablename
if you are taking in the same server done mention as localhost just
switch user as postgress and give the above command mentioned.
manjula hettiarachchi wrote:
>Hello List
>
>I am using postgresql 7.4.7 in a voip production
>setup.
>I have been using pg_dump -Fc for regular backing up.
>Since yesterday i am getting the following error for
>the command:
>
>root# pg_dump -h 'localhost' voipdb -t voipcall -Fc -f
>voipcall.bak
>
>The error is :
>
>pg_dump: ERROR: invalid memory alloc request size
>4294967293
>pg_dump: SQL command to dump the contents of table
>"voipcall" failed: PQendcopy() failed.
>pg_dump: Error message from server: ERROR: invalid
>memory alloc request size 4294967293
>pg_dump: The command was: COPY public.voipcall (id,
>accountid, .........., prefix) TO stdout;
>
>However when i tried to Vacuum analyze the same table
>its fine and no errors. Also the SQL access to the
>same table runs fine without any errors.
>
>Only the pg_dump is failing for this particular table.
>
>Can anyone suggest a method to fix this?
>
>Thanks in advance
>
>Manjula
>
>
>
>__________________________________________________
>Do You Yahoo!?
>Tired of spam? Yahoo! Mail has the best spam protection around
>http://mail.yahoo.com
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: Don't 'kill -9' the postmaster
>
>
>
--
Thanks & Regards,
Dilipkumar
DBA Support
********** DISCLAIMER **********
Information contained and transmitted by this E-MAIL is proprietary to
Sify Limited and is intended for use only by the individual or entity to
which it is addressed, and may contain information that is privileged,
confidential or exempt from disclosure under applicable law. If this is a
forwarded message, the content of this E-MAIL may not have been sent with
the authority of the Company. If you are not the intended recipient, an
agent of the intended recipient or a person responsible for delivering the
information to the named recipient, you are notified that any use,
distribution, transmission, printing, copying or dissemination of this
information in any way or in any manner is strictly prohibited. If you have
received this communication in error, please delete this mail & notify us
immediately at admin@sifycorp.com
Watch India vs. England LIVE, Hot videos and more only on Sify Max! Click Here. www.sifymax.com
Get to see what's happening in your favourite City on Bangalore Live! www.bangalorelive.in
^ permalink raw reply [nested|flat] 40+ messages in thread
* FWD: [ADMIN] pg_dump error
2006-07-06 12:25 pg_dump error manjula hettiarachchi <manjula_55@yahoo.com>
2006-07-06 12:29 ` Re: pg_dump error Dilipkumar <dilipkumar_parikh@sifycorp.com>
@ 2006-07-06 12:52 ` Guido Barosio <gbarosio@gmail.com>
2006-07-07 04:38 ` Re: FWD: [ADMIN] pg_dump error Christopher Browne <cbbrowne@acm.org>
2006-07-07 11:20 ` Re: FWD: [ADMIN] pg_dump error Robert Treat <xzilla@users.sourceforge.net>
0 siblings, 2 replies; 40+ messages in thread
From: Guido Barosio @ 2006-07-06 12:52 UTC (permalink / raw)
To: ; +Cc: pgsql-advocacy <pgsql-advocacy@postgresql.org>
How come?
Where does the "postgress" word comes from? I get mad when I read the double ss.
Progress Software ?! It's not that famous / big / popular.
g.-
On 7/6/06, Dilipkumar <dilipkumar_parikh@sifycorp.com> wrote:
> Hi,
>
> If you are trying to take a table dump try using this
>
> pd_dump databasename -t tablename
>
> if you are taking in the same server done mention as localhost just
> switch user as postgress and give the above command mentioned.
>
> manjula hettiarachchi wrote:
>
> >Hello List
> >
> >I am using postgresql 7.4.7 in a voip production
> >setup.
> >I have been using pg_dump -Fc for regular backing up.
> >Since yesterday i am getting the following error for
> >the command:
> >
> >root# pg_dump -h 'localhost' voipdb -t voipcall -Fc -f
> >voipcall.bak
> >
> >The error is :
> >
> >pg_dump: ERROR: invalid memory alloc request size
> >4294967293
> >pg_dump: SQL command to dump the contents of table
> >"voipcall" failed: PQendcopy() failed.
> >pg_dump: Error message from server: ERROR: invalid
> >memory alloc request size 4294967293
> >pg_dump: The command was: COPY public.voipcall (id,
> >accountid, .........., prefix) TO stdout;
> >
> >However when i tried to Vacuum analyze the same table
> >its fine and no errors. Also the SQL access to the
> >same table runs fine without any errors.
> >
> >Only the pg_dump is failing for this particular table.
> >
> >Can anyone suggest a method to fix this?
> >
> >Thanks in advance
> >
> >Manjula
> >
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Tired of spam? Yahoo! Mail has the best spam protection around
> >http://mail.yahoo.com
> >
> >---------------------------(end of broadcast)---------------------------
> >TIP 2: Don't 'kill -9' the postmaster
> >
> >
> >
>
>
> --
> Thanks & Regards,
> Dilipkumar
> DBA Support
>
> ********** DISCLAIMER **********
> Information contained and transmitted by this E-MAIL is proprietary to
> Sify Limited and is intended for use only by the individual or entity to
> which it is addressed, and may contain information that is privileged,
> confidential or exempt from disclosure under applicable law. If this is a
> forwarded message, the content of this E-MAIL may not have been sent with
> the authority of the Company. If you are not the intended recipient, an
> agent of the intended recipient or a person responsible for delivering the
> information to the named recipient, you are notified that any use,
> distribution, transmission, printing, copying or dissemination of this
> information in any way or in any manner is strictly prohibited. If you have
> received this communication in error, please delete this mail & notify us
> immediately at admin@sifycorp.com
>
> Watch India vs. England LIVE, Hot videos and more only on Sify Max! Click Here. www.sifymax.com
>
> Get to see what's happening in your favourite City on Bangalore Live! www.bangalorelive.in
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
Guido Barosio
-----------------------
http://www.globant.com
guido.barosio@globant.com
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: FWD: [ADMIN] pg_dump error
2006-07-06 12:25 pg_dump error manjula hettiarachchi <manjula_55@yahoo.com>
2006-07-06 12:29 ` Re: pg_dump error Dilipkumar <dilipkumar_parikh@sifycorp.com>
2006-07-06 12:52 ` FWD: [ADMIN] pg_dump error Guido Barosio <gbarosio@gmail.com>
@ 2006-07-07 04:38 ` Christopher Browne <cbbrowne@acm.org>
1 sibling, 0 replies; 40+ messages in thread
From: Christopher Browne @ 2006-07-07 04:38 UTC (permalink / raw)
To: pgsql-advocacy@postgresql.org
Quoth gbarosio@gmail.com ("Guido Barosio"):
> Where does the "postgress" word comes from? I get mad when I read the double ss.
> Progress Software ?! It's not that famous / big / popular.
"Postgres" was a successor project to "University Ingres."
So s/In/Post/g is the source.
There isn't any material amount of common code between the two
database projects, but they were started by the same professor...
--
wm(X,Y):-write(X),write('@'),write(Y). wm('cbbrowne','acm.org').
http://cbbrowne.com/info/lsf.html
The easiest way to find something lost around the house is to buy a
replacement.
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: FWD: [ADMIN] pg_dump error
2006-07-06 12:25 pg_dump error manjula hettiarachchi <manjula_55@yahoo.com>
2006-07-06 12:29 ` Re: pg_dump error Dilipkumar <dilipkumar_parikh@sifycorp.com>
2006-07-06 12:52 ` FWD: [ADMIN] pg_dump error Guido Barosio <gbarosio@gmail.com>
@ 2006-07-07 11:20 ` Robert Treat <xzilla@users.sourceforge.net>
1 sibling, 0 replies; 40+ messages in thread
From: Robert Treat @ 2006-07-07 11:20 UTC (permalink / raw)
To: pgsql-advocacy@postgresql.org; +Cc: Guido Barosio <gbarosio@gmail.com>
On Thursday 06 July 2006 08:52, Guido Barosio wrote:
> How come?
>
> Where does the "postgress" word comes from? I get mad when I read the
> double ss. Progress Software ?! It's not that famous / big / popular.
>
you forgot /good :-P
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
^ permalink raw reply [nested|flat] 40+ messages in thread
* Fwd: Re: pg_dump error
@ 2006-07-07 04:17 manjula hettiarachchi <manjula_55@yahoo.com>
0 siblings, 0 replies; 40+ messages in thread
From: manjula hettiarachchi @ 2006-07-07 04:17 UTC (permalink / raw)
To: pgsql-admin
Hi,
Already doing Vacuum analize procedure on daily basis.
But the pg_dump fails on ONLY one table.
That table works normal for other operations. But we
are feeling uncomfortable to keep using that table as
unable to backup.
Can anyone give a hint how to fix the pg_dump issue
Thanks
Manjula
--- Dilipkumar <dilipkumar_parikh@sifycorp.com> wrote:
> Date: Thu, 06 Jul 2006 20:21:53 +0530
> From: Dilipkumar <dilipkumar_parikh@sifycorp.com>
> To: manjula hettiarachchi <manjula_55@yahoo.com>
> Subject: Re: [ADMIN] pg_dump error
>
> Hi,
>
> Or try to run vaccum scripts this will help you out.
>
> manjula hettiarachchi wrote:
>
> >Hi
> >
> >How do I optimize?
> >
> >Thanks in advance
> >
> >Manjula
> >
> >--- Dilipkumar <dilipkumar_parikh@sifycorp.com>
> wrote:
> >
> >
> >
> >>Hi,
> >>
> >>I think if the table is too large then try to
> >>optimize the table and
> >>check it.
> >>then you shall try the command mentioned.
> >>
> >>manjula hettiarachchi wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>Thanks for the reply.
> >>>
> >>>Actually this is the full command i used:
> >>>
> >>>pg_dump database_name -t tablename -h
> 'localhost'
> >>>
> >>>
> >>-U
> >>
> >>
> >>>postgres -Fc
> >>>
> >>>As this table is too large cannot use the text
> mode
> >>>dump. However all other tables get properly
> >>>
> >>>
> >>backed-up
> >>
> >>
> >>>by the above command. Only this particular table
> is
> >>>giving the error.
> >>>
> >>>Also this table seem normal for all other
> >>>
> >>>
> >>functions,
> >>
> >>
> >>>and only the dump is not working for it.
> >>>
> >>>Any Idea?
> >>>
> >>>Regards
> >>>
> >>>Manjula
> >>>
> >>>
> >>>--- Dilipkumar <dilipkumar_parikh@sifycorp.com>
> >>>
> >>>
> >>wrote:
> >>
> >>
> >>>
> >>>
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>If you are trying to take a table dump try using
> >>>>this
> >>>>
> >>>>pd_dump databasename -t tablename
> >>>>
> >>>>if you are taking in the same server done
> mention
> >>>>
> >>>>
> >>as
> >>
> >>
> >>>>localhost just
> >>>>switch user as postgress and give the above
> >>>>
> >>>>
> >>command
> >>
> >>
> >>>>mentioned.
> >>>>
> >>>>manjula hettiarachchi wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Hello List
> >>>>>
> >>>>>I am using postgresql 7.4.7 in a voip
> production
> >>>>>setup.
> >>>>>I have been using pg_dump -Fc for regular
> backing
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>up.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Since yesterday i am getting the following
> error
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>for
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>the command:
> >>>>>
> >>>>>root# pg_dump -h 'localhost' voipdb -t voipcall
> >>>>>
> >>>>>
> >>-Fc
> >>
> >>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>-f
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>voipcall.bak
> >>>>>
> >>>>>The error is :
> >>>>>
> >>>>>pg_dump: ERROR: invalid memory alloc request
> >>>>>
> >>>>>
> >>size
> >>
> >>
> >>>>>4294967293
> >>>>>pg_dump: SQL command to dump the contents of
> >>>>>
> >>>>>
> >>table
> >>
> >>
> >>>>>"voipcall" failed: PQendcopy() failed.
> >>>>>pg_dump: Error message from server: ERROR:
> >>>>>
> >>>>>
> >>invalid
> >>
> >>
> >>>>>memory alloc request size 4294967293
> >>>>>pg_dump: The command was: COPY public.voipcall
> >>>>>
> >>>>>
> >>(id,
> >>
> >>
> >>>>>accountid, .........., prefix) TO stdout;
> >>>>>
> >>>>>However when i tried to Vacuum analyze the same
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>table
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>its fine and no errors. Also the SQL access to
> >>>>>
> >>>>>
> >>the
> >>
> >>
> >>>>>same table runs fine without any errors.
> >>>>>
> >>>>>Only the pg_dump is failing for this particular
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>table.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>Can anyone suggest a method to fix this?
> >>>>>
> >>>>>Thanks in advance
> >>>>>
> >>>>>Manjula
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
>
>>>>__________________________________________________
> >>>>
> >>>>
> >>>>>Do You Yahoo!?
> >>>>>Tired of spam? Yahoo! Mail has the best spam
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>protection around
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>http://mail.yahoo.com
> >>>>>
> >>>>>---------------------------(end of
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>broadcast)---------------------------
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>TIP 2: Don't 'kill -9' the postmaster
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>--
> >>>>Thanks & Regards,
> >>>>Dilipkumar
> >>>>DBA Support
> >>>>
> >>>>********** DISCLAIMER **********
> >>>>Information contained and transmitted by this
> >>>>
> >>>>
> >>E-MAIL
> >>
> >>
> >>>>is proprietary to
> >>>>Sify Limited and is intended for use only by the
> >>>>individual or entity to
> >>>>which it is addressed, and may contain
> information
> >>>>that is privileged,
> >>>>confidential or exempt from disclosure under
> >>>>applicable law. If this is a
> >>>>forwarded message, the content of this E-MAIL
> may
> >>>>not have been sent with
> >>>>the authority of the Company. If you are not the
> >>>>intended recipient, an
> >>>>agent of the intended recipient or a person
> >>>>responsible for delivering the
> >>>>information to the named recipient, you are
> >>>>notified that any use,
> >>>>distribution, transmission, printing, copying or
> >>>>dissemination of this
> >>>>information in any way or in any manner is
> >>>>
> >>>>
> >>strictly
> >>
> >>
> >>>>prohibited. If you have
> >>>>received this communication in error, please
> >>>>
> >>>>
> >>delete
> >>
> >>
> >>>>this mail & notify us
> >>>>immediately at admin@sifycorp.com
> >>>>
> >>>>Watch India vs. England LIVE, Hot videos and
> more
> >>>>only on Sify Max! Click Here. www.sifymax.com
> >>>>
> >>>>Get to see what's happening in your favourite
> City
> >>>>on Bangalore Live! www.bangalorelive.in
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
>
>>>__________________________________________________
> >>>Do You Yahoo!?
> >>>Tired of spam? Yahoo! Mail has the best spam
> >>>
> >>>
> >>protection around
> >>
> >>
> >>>http://mail.yahoo.com
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >=== message truncated ===
> >
> >
> >__________________________________________________
> >Do You Yahoo!?
> >Tired of spam? Yahoo! Mail has the best spam
> protection around
> >http://mail.yahoo.com
> >
> >
> >
>
>
> --
> Thanks & Regards,
> Dilipkumar
> DBA Support
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2007-02-28 19:17 Karthikeyan Sundaram <skarthi98@hotmail.com>
2007-02-28 19:31 ` Re: pg_dump error Joshua D. Drake <jd@commandprompt.com>
0 siblings, 1 reply; 40+ messages in thread
From: Karthikeyan Sundaram @ 2007-02-28 19:17 UTC (permalink / raw)
To: pgsql-admin; pgsql-sql@postgresql.org
Hi,
I am using 8.2.1 on my dev server.
When I do a pg_dump, I am getting an error message.
pg_dump -U postgres podcast -t channel
pg_dump: symbol lookup error: pg_dump: undefined symbol: PQescapeStringConn
How can I resolved this? What may be the problem?
Because of this, I am not able to dump anything.
Regards
skarthi
_________________________________________________________________
Play Flexicon: the crossword game that feeds your brain. PLAY now for FREE.
http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2007-02-28 19:17 pg_dump error Karthikeyan Sundaram <skarthi98@hotmail.com>
@ 2007-02-28 19:31 ` Joshua D. Drake <jd@commandprompt.com>
2007-02-28 19:35 ` Re: pg_dump error Karthikeyan Sundaram <skarthi98@hotmail.com>
0 siblings, 1 reply; 40+ messages in thread
From: Joshua D. Drake @ 2007-02-28 19:31 UTC (permalink / raw)
To: Karthikeyan Sundaram <skarthi98@hotmail.com>; +Cc: pgsql-admin; pgsql-sql@postgresql.org
Karthikeyan Sundaram wrote:
> Hi,
>
> I am using 8.2.1 on my dev server.
>
> When I do a pg_dump, I am getting an error message.
>
> pg_dump -U postgres podcast -t channel
>
> pg_dump: symbol lookup error: pg_dump: undefined symbol: PQescapeStringConn
>
> How can I resolved this? What may be the problem?
>
> Because of this, I am not able to dump anything.
Sounds like you have two different versions of pg_dump on your box. Did
you recently try to upgrade?
Sincerely,
Joshua D. Drake
>
>
> Regards
> skarthi
>
> _________________________________________________________________
> Play Flexicon: the crossword game that feeds your brain. PLAY now for
> FREE. http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2007-02-28 19:17 pg_dump error Karthikeyan Sundaram <skarthi98@hotmail.com>
2007-02-28 19:31 ` Re: pg_dump error Joshua D. Drake <jd@commandprompt.com>
@ 2007-02-28 19:35 ` Karthikeyan Sundaram <skarthi98@hotmail.com>
2007-03-02 06:12 ` Re: [SQL] pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 40+ messages in thread
From: Karthikeyan Sundaram @ 2007-02-28 19:35 UTC (permalink / raw)
To: jd@commandprompt.com; +Cc: pgsql-admin; pgsql-sql@postgresql.org
Hi Joshua,
Thanks for your reply. No, I recently installed (fresh installation)
from scratch.
Regards
skarthi
>From: "Joshua D. Drake" <jd@commandprompt.com>
>To: Karthikeyan Sundaram <skarthi98@hotmail.com>
>CC: pgsql-admin@postgresql.org, pgsql-sql@postgresql.org
>Subject: Re: [ADMIN] pg_dump error
>Date: Wed, 28 Feb 2007 11:31:01 -0800
>
>Karthikeyan Sundaram wrote:
> > Hi,
> >
> > I am using 8.2.1 on my dev server.
> >
> > When I do a pg_dump, I am getting an error message.
> >
> > pg_dump -U postgres podcast -t channel
> >
> > pg_dump: symbol lookup error: pg_dump: undefined symbol:
>PQescapeStringConn
> >
> > How can I resolved this? What may be the problem?
> >
> > Because of this, I am not able to dump anything.
>
>Sounds like you have two different versions of pg_dump on your box. Did
>you recently try to upgrade?
>
>Sincerely,
>
>Joshua D. Drake
>
>
> >
> >
> > Regards
> > skarthi
> >
> > _________________________________________________________________
> > Play Flexicon: the crossword game that feeds your brain. PLAY now for
> > FREE.
>http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Have you searched our list archives?
> >
> > http://archives.postgresql.org
> >
>
>
>--
>
> === The PostgreSQL Company: Command Prompt, Inc. ===
>Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
>Providing the most comprehensive PostgreSQL solutions since 1997
> http://www.commandprompt.com/
>
>Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
>PostgreSQL Replication: http://www.commandprompt.com/products/
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: You can help support the PostgreSQL project by donating at
>
> http://www.postgresql.org/about/donate
_________________________________________________________________
Mortgage rates as low as 4.625% - Refinance $150,000 loan for $579 a month.
Intro*Terms
https://www2.nextag.com/goto.jsp?product=100000035&url=%2fst.jsp&tm=y&search=mortgage_te...
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: [SQL] pg_dump error
2007-02-28 19:17 pg_dump error Karthikeyan Sundaram <skarthi98@hotmail.com>
2007-02-28 19:31 ` Re: pg_dump error Joshua D. Drake <jd@commandprompt.com>
2007-02-28 19:35 ` Re: pg_dump error Karthikeyan Sundaram <skarthi98@hotmail.com>
@ 2007-03-02 06:12 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 40+ messages in thread
From: Tom Lane @ 2007-03-02 06:12 UTC (permalink / raw)
To: Karthikeyan Sundaram <skarthi98@hotmail.com>; +Cc: jd@commandprompt.com; pgsql-admin; pgsql-sql@postgresql.org
"Karthikeyan Sundaram" <skarthi98@hotmail.com> writes:
> Thanks for your reply. No, I recently installed (fresh installation)
> from scratch.
Well, your pg_dump seems to be finding an older version of libpq.so from
somewhere. Check for a pre-existing postgresql package.
regards, tom lane
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump error
@ 2015-07-20 10:51 Campbell, Lance <lance@illinois.edu>
2015-07-20 11:23 ` Re: pg_dump error Campbell, Lance <lance@illinois.edu>
0 siblings, 1 reply; 40+ messages in thread
From: Campbell, Lance @ 2015-07-20 10:51 UTC (permalink / raw)
To: pgsql-admin
Postgresql 9.4.x
I am performing the following pg_dump command:
pg_dump -U username -h localhost --jobs=3 --format=d --compress=0 databasename -f databasename.20150720
I am getting this error:
pg_dump: [parallel archiver] could not get relation name for OID 58363761: connection not open
How can I work around this issue? Should I just not used --jobs=3 when backing up the full database?
Lance Campbell
Software Architect
Web Services at the University of Illinois
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2015-07-20 10:51 pg_dump error Campbell, Lance <lance@illinois.edu>
@ 2015-07-20 11:23 ` Campbell, Lance <lance@illinois.edu>
2015-07-20 12:31 ` Re: pg_dump error Campbell, Lance <lance@illinois.edu>
2015-07-20 13:59 ` Re: pg_dump error Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 40+ messages in thread
From: Campbell, Lance @ 2015-07-20 11:23 UTC (permalink / raw)
To: Campbell, Lance <lance@illinois.edu>; pgsql-admin
As a follow-up I ran this command:
pg_dump -U username -h localhost databasename -f databasename.20150720
I get this in the console:
pg_dump: [archiver (db)] query failed: SSL error: unexpected message
pg_dump: [archiver (db)] query was: SET search_path = calendar, pg_catalog
PG Admin is telling me the database is 57 G.
I was able to do the following command in order to just backup the "calendar" schema with data:
pg_dump -U username -h localhost --schema=calendar databasename -f calendar.20150720
So why am I unable to backup my entire database?
Lance
-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Campbell, Lance
Sent: Monday, July 20, 2015 5:52 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pg_dump error
Postgresql 9.4.x
I am performing the following pg_dump command:
pg_dump -U username -h localhost --jobs=3 --format=d --compress=0 databasename -f databasename.20150720
I am getting this error:
pg_dump: [parallel archiver] could not get relation name for OID 58363761: connection not open
How can I work around this issue? Should I just not used --jobs=3 when backing up the full database?
Lance Campbell
Software Architect
Web Services at the University of Illinois
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2015-07-20 10:51 pg_dump error Campbell, Lance <lance@illinois.edu>
2015-07-20 11:23 ` Re: pg_dump error Campbell, Lance <lance@illinois.edu>
@ 2015-07-20 12:31 ` Campbell, Lance <lance@illinois.edu>
2015-07-20 13:03 ` Re: pg_dump error Campbell, Lance <lance@illinois.edu>
1 sibling, 1 reply; 40+ messages in thread
From: Campbell, Lance @ 2015-07-20 12:31 UTC (permalink / raw)
To: pgsql-admin
Postgresql 9.4.4
Linux Redhat
When I trigger pg_dump of the database I am doing it locally on the server running postgresql. I also went in to pg_hba.conf and made sure that the local user does not use SSL.
I know our servers were patched recently. Would there ever be a case where we have to rebuild build, compile and make, postgresql because of changes to the SSL libraries?
Lance
-----Original Message-----
From: Campbell, Lance
Sent: Monday, July 20, 2015 6:23 AM
To: Campbell, Lance <lance@illinois.edu>; pgsql-admin@postgresql.org
Subject: RE: pg_dump error
As a follow-up I ran this command:
pg_dump -U username -h localhost databasename -f databasename.20150720
I get this in the console:
pg_dump: [archiver (db)] query failed: SSL error: unexpected message
pg_dump: [archiver (db)] query was: SET search_path = calendar, pg_catalog
PG Admin is telling me the database is 57 G.
I was able to do the following command in order to just backup the "calendar" schema with data:
pg_dump -U username -h localhost --schema=calendar databasename -f calendar.20150720
So why am I unable to backup my entire database?
Lance
-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Campbell, Lance
Sent: Monday, July 20, 2015 5:52 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pg_dump error
Postgresql 9.4.x
I am performing the following pg_dump command:
pg_dump -U username -h localhost --jobs=3 --format=d --compress=0 databasename -f databasename.20150720
I am getting this error:
pg_dump: [parallel archiver] could not get relation name for OID 58363761: connection not open
How can I work around this issue? Should I just not used --jobs=3 when backing up the full database?
Lance Campbell
Software Architect
Web Services at the University of Illinois
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2015-07-20 10:51 pg_dump error Campbell, Lance <lance@illinois.edu>
2015-07-20 11:23 ` Re: pg_dump error Campbell, Lance <lance@illinois.edu>
2015-07-20 12:31 ` Re: pg_dump error Campbell, Lance <lance@illinois.edu>
@ 2015-07-20 13:03 ` Campbell, Lance <lance@illinois.edu>
0 siblings, 0 replies; 40+ messages in thread
From: Campbell, Lance @ 2015-07-20 13:03 UTC (permalink / raw)
To: Campbell, Lance <lance@illinois.edu>; pgsql-admin
I contacted my server manager to make sure you have the proper version numbers of the software I am using. But I may or may not have compiled postgresql with the openSSL library listed below. The server managers do regular patching.
Postgresql 9.4.4
RHEL version is 6.6.
OpenSSL version is 1.0.1e-30.el6_6.11
Thanks,
Lance Campbell
-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Campbell, Lance
Sent: Monday, July 20, 2015 7:31 AM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] pg_dump error
Postgresql 9.4.4
Linux Redhat
When I trigger pg_dump of the database I am doing it locally on the server running postgresql. I also went in to pg_hba.conf and made sure that the local user does not use SSL.
I know our servers were patched recently. Would there ever be a case where we have to rebuild build, compile and make, postgresql because of changes to the SSL libraries?
Lance
-----Original Message-----
From: Campbell, Lance
Sent: Monday, July 20, 2015 6:23 AM
To: Campbell, Lance <lance@illinois.edu>; pgsql-admin@postgresql.org
Subject: RE: pg_dump error
As a follow-up I ran this command:
pg_dump -U username -h localhost databasename -f databasename.20150720
I get this in the console:
pg_dump: [archiver (db)] query failed: SSL error: unexpected message
pg_dump: [archiver (db)] query was: SET search_path = calendar, pg_catalog
PG Admin is telling me the database is 57 G.
I was able to do the following command in order to just backup the "calendar" schema with data:
pg_dump -U username -h localhost --schema=calendar databasename -f calendar.20150720
So why am I unable to backup my entire database?
Lance
-----Original Message-----
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Campbell, Lance
Sent: Monday, July 20, 2015 5:52 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pg_dump error
Postgresql 9.4.x
I am performing the following pg_dump command:
pg_dump -U username -h localhost --jobs=3 --format=d --compress=0 databasename -f databasename.20150720
I am getting this error:
pg_dump: [parallel archiver] could not get relation name for OID 58363761: connection not open
How can I work around this issue? Should I just not used --jobs=3 when backing up the full database?
Lance Campbell
Software Architect
Web Services at the University of Illinois
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump error
2015-07-20 10:51 pg_dump error Campbell, Lance <lance@illinois.edu>
2015-07-20 11:23 ` Re: pg_dump error Campbell, Lance <lance@illinois.edu>
@ 2015-07-20 13:59 ` Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 40+ messages in thread
From: Tom Lane @ 2015-07-20 13:59 UTC (permalink / raw)
To: Campbell, Lance <lance@illinois.edu>; +Cc: pgsql-admin
"Campbell, Lance" <lance@illinois.edu> writes:
> As a follow-up I ran this command:
> pg_dump -U username -h localhost databasename -f databasename.20150720
> I get this in the console:
> pg_dump: [archiver (db)] query failed: SSL error: unexpected message
> pg_dump: [archiver (db)] query was: SET search_path = calendar, pg_catalog
That looks like you've run into the renegotiation bug that Red Hat
introduced in their last openssl patch:
https://bugzilla.redhat.com/show_bug.cgi?id=1234487
So basically things will work until you exceed a couple gigabytes of
traffic on the connection, and then bang.
The workaround we're recommending to people is to set
ssl_renegotiation_limit to zero (disable it) in postgresql.conf, as
renegotiation seems to create way more problems than it fixes (this
RH bug was very far from the first such problem, and it's not likely
to be the last either).
See recent discussions on pgsql-hackers, where it was more or less
agreed that we're going to remove the feature altogether in the future.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 40+ messages in thread
* pg_dump: error
@ 2023-02-22 16:17 Alessandro Papa - Infolab <a.papa@infolabonline.com>
2023-02-22 16:44 ` Re: pg_dump: error David G. Johnston <david.g.johnston@gmail.com>
2023-02-22 17:15 ` Re: pg_dump: error Alvaro Herrera <alvherre@alvh.no-ip.org>
0 siblings, 2 replies; 40+ messages in thread
From: Alessandro Papa - Infolab @ 2023-02-22 16:17 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>; +Cc: Silvio Scattaglia - Infolab <s.scattaglia@infolabonline.com>
Hi, i have a PostgreSQL db with 9.8 version,
When I try to make a backup I get this error:
<pg_dump: error: schema with OID 2535211008 does not exist>
I had already searched on the table "pg_conversion" but didn't find that OID, idem on "pg_namespace" or "pg_type"
I had searched on forum but I have not found anything.
Thank you for your help
Disclaimer :
Le informazioni contenute nella presente comunicazione e i relativi allegati possono contenere informazioni riservate e sono, comunque, destinate dalla Infolab s.n.c. esclusivamente alle persone o alla Societ? destinatarie del messaggio stesso. Qualsiasi utilizzo non autorizzato del presente messaggio e/o dei suoi allegati da parte di qualsiasi soggetto diverso dal destinatario ? proibita, sia ai sensi dell'art. 616 c.p., che ai sensi del D.Lgs. n. 196/2003. Se avete ricevuto questo messaggio per errore, vi preghiamo di distruggerlo e di informarci immediatamente per telefono allo +39 0523 716018 o inviando un messaggio all'indirizzo e-mail info@infolabonline.com <mailto:info@infolabonline.com>
This message contains confidential information and is intended only for the Recipients. If you are not the Recipients you should not disseminate, distribute or copy this e-mail. Please notify info@infolabonline.com <mailto:info@infolabonline.com> immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. Infolab therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump: error
2023-02-22 16:17 pg_dump: error Alessandro Papa - Infolab <a.papa@infolabonline.com>
@ 2023-02-22 16:44 ` David G. Johnston <david.g.johnston@gmail.com>
1 sibling, 0 replies; 40+ messages in thread
From: David G. Johnston @ 2023-02-22 16:44 UTC (permalink / raw)
To: Alessandro Papa - Infolab <a.papa@infolabonline.com>; +Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>; Silvio Scattaglia - Infolab <s.scattaglia@infolabonline.com>
On Wed, Feb 22, 2023 at 9:39 AM Alessandro Papa - Infolab <
a.papa@infolabonline.com> wrote:
> Hi, i have a PostgreSQL db with 9.8 version,
>
> When I try to make a backup I get this error:
>
> <pg_dump: error: schema with OID 2535211008 does not exist>
>
>
>
> I had already searched on the table “pg_conversion” but didn’t find that
> OID, idem on “pg_namespace” or “pg_type”
>
> I had searched on forum but I have not found anything.
>
>
>
> Thank you for your help
>
>
>
"Version 9.8" isn't one of our release versions.
But if your catalog is corrupted that is not good and may require invasive
surgery. But in any case this is not a valid bug report. Please ask for
assistance in repairing your system in a more appropriate forum - the
pgsql-admin list being probably the most appropriate choice.
David J.
^ permalink raw reply [nested|flat] 40+ messages in thread
* Re: pg_dump: error
2023-02-22 16:17 pg_dump: error Alessandro Papa - Infolab <a.papa@infolabonline.com>
@ 2023-02-22 17:15 ` Alvaro Herrera <alvherre@alvh.no-ip.org>
1 sibling, 0 replies; 40+ messages in thread
From: Alvaro Herrera @ 2023-02-22 17:15 UTC (permalink / raw)
To: Alessandro Papa - Infolab <a.papa@infolabonline.com>; +Cc: pgsql-admin@lists.postgresql.org, Silvio Scattaglia - Infolab <s.scattaglia@infolabonline.com>
CCing pgsql-admin, removed -bugs.
On 2023-Feb-22, Alessandro Papa - Infolab wrote:
> Hi, i have a PostgreSQL db with 9.8 version,
You'll have to figure out exactly what version it is, because 9.8 it is
not.
> When I try to make a backup I get this error:
> <pg_dump: error: schema with OID 2535211008 does not exist>
>
> I had already searched on the table "pg_conversion" but didn't find that OID, idem on "pg_namespace" or "pg_type"
> I had searched on forum but I have not found anything.
A reference to a schema could come from almost any other catalog, not
just pg_conversion. (Note that a "namespace" is essentially the same as
a "schema" in our usage). That particular error in the 9.6.24 pg_dump
source could come from
1 4218 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getTypes>>
2 4432 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getOperators>>
3 4519 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getCollations>>
4 4600 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getConversions>>
5 4765 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getOpclasses>>
6 4853 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getOpfamilies>>
7 5060 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getAggregates>>
8 5328 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getFuncs>>
9 6114 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getTables>>
10 8450 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getTSParsers>>
11 8534 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getTSDictionaries>>
12 8615 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getTSTemplates>>
13 8693 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getTSConfigurations>>
14 9142 /pgsql/source/REL9_6_STABLE/src/bin/pg_dump/pg_dump.c <<getDefaultACLs>>
which are the places that call findNamespace, where the error message
appears.
Give that a look and see if any clues arise. You can follow up here
afterwards for more ...
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
^ permalink raw reply [nested|flat] 40+ messages in thread
end of thread, other threads:[~2023-02-22 17:15 UTC | newest]
Thread overview: 40+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-04-17 03:02 pg_dump error Joe Conway <jconway2@home.com>
2001-03-28 12:07 pg_dump ERROR ....... agichen@kimo.com
2002-02-25 21:32 pg_dump error Srinivasa Rao Chava <s.chava@wcom.com>
2002-02-25 22:42 ` Stephan Szabo <sszabo@megazone23.bigpanda.com>
2002-02-25 23:12 ` Tom Lane <tgl@sss.pgh.pa.us>
2002-10-01 15:52 pg_dump error Ferdinand Smit <ferdinand@telegraafnet.nl>
2002-10-01 17:10 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-11-06 17:35 pg_dump error David C. Brown <dbrown@centennialwines.com>
2003-11-06 18:20 ` Tom Lane <tgl@sss.pgh.pa.us>
2003-11-06 18:23 ` David C. Brown <dbrown@centennialwines.com>
2004-06-29 09:38 pg_dump Error Nigel Bishop <Nigel.Bishop@ioko.com>
2004-06-29 11:27 ` Re: pg_dump Error Guido Barosio <gbarosio@sinectis.com.ar>
2004-06-29 14:16 ` Re: pg_dump Error Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 09:50 pg_dump error Adam Witney <awitney@sgul.ac.uk>
2005-09-07 14:54 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:08 ` Adam Witney <awitney@sgul.ac.uk>
2005-09-07 15:28 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 15:40 ` Adam Witney <awitney@sgul.ac.uk>
2005-09-07 15:56 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-09-07 14:55 ` Michael Fuhr <mike@fuhr.org>
2005-09-28 15:13 pg_dump error Jerry Cadet <jjrc71@hotmail.com>
2005-10-06 10:33 PG_DUMP Error Cédric Buschini <cbuschini@carax.com>
2006-07-06 12:25 pg_dump error manjula hettiarachchi <manjula_55@yahoo.com>
2006-07-06 12:29 ` Dilipkumar <dilipkumar_parikh@sifycorp.com>
2006-07-06 12:52 ` Guido Barosio <gbarosio@gmail.com>
2006-07-07 04:38 ` Christopher Browne <cbbrowne@acm.org>
2006-07-07 11:20 ` Robert Treat <xzilla@users.sourceforge.net>
2006-07-07 04:17 Fwd: Re: pg_dump error manjula hettiarachchi <manjula_55@yahoo.com>
2007-02-28 19:17 pg_dump error Karthikeyan Sundaram <skarthi98@hotmail.com>
2007-02-28 19:31 ` Joshua D. Drake <jd@commandprompt.com>
2007-02-28 19:35 ` Karthikeyan Sundaram <skarthi98@hotmail.com>
2007-03-02 06:12 ` Tom Lane <tgl@sss.pgh.pa.us>
2015-07-20 10:51 pg_dump error Campbell, Lance <lance@illinois.edu>
2015-07-20 11:23 ` Campbell, Lance <lance@illinois.edu>
2015-07-20 12:31 ` Campbell, Lance <lance@illinois.edu>
2015-07-20 13:03 ` Campbell, Lance <lance@illinois.edu>
2015-07-20 13:59 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-02-22 16:17 pg_dump: error Alessandro Papa - Infolab <a.papa@infolabonline.com>
2023-02-22 16:44 ` Re: pg_dump: error David G. Johnston <david.g.johnston@gmail.com>
2023-02-22 17:15 ` Re: pg_dump: error Alvaro Herrera <alvherre@alvh.no-ip.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox