pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedError on pg_dumpall
7+ messages / 5 participants
[nested] [flat]
* Error on pg_dumpall
@ 2008-04-29 13:59 Carol Walter <walterc@indiana.edu>
0 siblings, 2 replies; 7+ messages in thread
From: Carol Walter @ 2008-04-29 13:59 UTC (permalink / raw)
To: pgsql-admin
Greetings,
I'm having a problem that I hope you can help me with. I am getting
the following error when I try to run pg_dumpall.
postgres@machine1:~$ /usr/local/pgsql/bin/pg_dumpall
pg_dumpall: could not connect to database "template1": could not
connect to server: No such file or directory
Is the server running locally and accepting
connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
If I run the command "psql template1", I can connect to template1
just fine. It looks like pg_dumpall may be looking for template1 in
the wrong place.
This is a new installation of postgresql 8.3 on a Debian Linux
machine. All my other machines are Solaris 10 running PostgreSQL 8.2.
Thanks,
Carol Walter
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Error on pg_dumpall
@ 2008-04-29 14:37 Julian v. Bock <bock@openit.de>
parent: Carol Walter <walterc@indiana.edu>
1 sibling, 0 replies; 7+ messages in thread
From: bock@openit.de @ 2008-04-29 14:37 UTC (permalink / raw)
To: pgsql-admin
Hi
>>>>> "CW" == Carol Walter <walterc@indiana.edu> writes:
CW> postgres@machine1:~$ /usr/local/pgsql/bin/pg_dumpall pg_dumpall:
CW> could not connect to database "template1": could not connect to
CW> server: No such file or directory Is the server running locally
CW> and accepting connections on Unix domain socket
CW> "/tmp/.s.PGSQL.5432"?
CW> If I run the command "psql template1", I can connect to template1
CW> just fine. It looks like pg_dumpall may be looking for template1
CW> in the wrong place.
Debian uses /var/run/postgresql instead of /tmp as directory for unix
domain sockets. Try
/usr/local/pgsql/bin/pg_dumpall -h /var/run/postgresql
--
Julian v. Bock Projektleitung Software-Entwicklung
OpenIT GmbH Tel +49 211 239 577-0
Jahnstr. 18 Fax +49 211 239 577-10
D-40215 Düsseldorf http://www.openit.de
________________________________________________________________
HRB 38815 Amtsgericht Düsseldorf USt-Id DE 812951861
Geschäftsführer:
Susanne Schultz, Oliver Haakert, Maurice Kemmann
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Error on pg_dumpall
@ 2008-04-29 14:45 Tom Lane <tgl@sss.pgh.pa.us>
parent: Carol Walter <walterc@indiana.edu>
1 sibling, 1 reply; 7+ messages in thread
From: Tom Lane @ 2008-04-29 14:45 UTC (permalink / raw)
To: Carol Walter <walterc@indiana.edu>; +Cc: pgsql-admin
Carol Walter <walterc@indiana.edu> writes:
> I'm having a problem that I hope you can help me with. I am getting
> the following error when I try to run pg_dumpall.
> postgres@machine1:~$ /usr/local/pgsql/bin/pg_dumpall
> pg_dumpall: could not connect to database "template1": could not
> connect to server: No such file or directory
> Is the server running locally and accepting
> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
> If I run the command "psql template1", I can connect to template1
> just fine.
Does "which psql" say that you're using the psql in
/usr/local/pgsql/bin?
It sounds to me a bit like you have two sets of PG programs with
different default port numbers compiled into them. Which port is
the server actually listening on?
> This is a new installation of postgresql 8.3 on a Debian Linux
> machine.
Debian is a rather nasty environment for custom-built PG installations,
because they have their own ideas of where to put the PG programs
and what port numbers they should run on. I'm thinking you are
connecting to a Debian-supplied postmaster on a non-standard port,
and not to your own installation at all.
regards, tom lane
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Error on pg_dumpall
@ 2008-05-01 14:09 Carol Walter <walterc@indiana.edu>
parent: Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 7+ messages in thread
From: Carol Walter @ 2008-05-01 14:09 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin
This turned out to be a wrapper versus binary issue. psql was
running under the wrapper. It ran fine. pg_dump wasn't but when we
corrected this it worked fine too.
This is the first time I've run into this and it's the first time
I've dealt with PostgreSQL on any but a Sparc running Solaris. I
don't know if the same thing happens with Solaris, but I'm going to
investigate just for interest.
Carol
On Apr 29, 2008, at 10:45 AM, Tom Lane wrote:
> Carol Walter <walterc@indiana.edu> writes:
>> I'm having a problem that I hope you can help me with. I am getting
>> the following error when I try to run pg_dumpall.
>
>> postgres@machine1:~$ /usr/local/pgsql/bin/pg_dumpall
>> pg_dumpall: could not connect to database "template1": could not
>> connect to server: No such file or directory
>> Is the server running locally and accepting
>> connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
>
>> If I run the command "psql template1", I can connect to template1
>> just fine.
>
> Does "which psql" say that you're using the psql in
> /usr/local/pgsql/bin?
>
> It sounds to me a bit like you have two sets of PG programs with
> different default port numbers compiled into them. Which port is
> the server actually listening on?
>
>> This is a new installation of postgresql 8.3 on a Debian Linux
>> machine.
>
> Debian is a rather nasty environment for custom-built PG
> installations,
> because they have their own ideas of where to put the PG programs
> and what port numbers they should run on. I'm thinking you are
> connecting to a Debian-supplied postmaster on a non-standard port,
> and not to your own installation at all.
>
> regards, tom lane
^ permalink raw reply [nested|flat] 7+ messages in thread
* Error on pg_dumpall
@ 2012-10-21 19:24 Terry Khatri <terrykhatri531@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Terry Khatri @ 2012-10-21 19:24 UTC (permalink / raw)
To: pgsql-admin
Hi
I am getting the following error msg when I do a pg_dumpall
-----
TK@OraLinux /usr/local/pgsql/backups
$ pg_dumpall -U sns84 > completebackup20121020,sql
pg_dump: schema with OID 74363 does not exist
pg_dumpall: pg_dump failed on database "bihistory", exiting
-----
I have set the logs to debug5 to catch where the problem is while taking
the dump but nothing shows up there.
If you have any ideas please help me.
And thanks to all for responding to my earlier post.
Rgds
T
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Error on pg_dumpall
@ 2012-10-23 05:15 Craig Ringer <ringerc@ringerc.id.au>
parent: Terry Khatri <terrykhatri531@gmail.com>
0 siblings, 1 reply; 7+ messages in thread
From: Craig Ringer @ 2012-10-23 05:15 UTC (permalink / raw)
To: Terry Khatri <terrykhatri531@gmail.com>; +Cc: pgsql-admin
On 10/22/2012 03:24 AM, Terry Khatri wrote:
> Hi
>
> I am getting the following error msg when I do a pg_dumpall
>
> -----
>
> TK@OraLinux /usr/local/pgsql/backups
> $ pg_dumpall -U sns84 > completebackup20121020,sql
> pg_dump: schema with OID 74363 does not exist
> pg_dumpall: pg_dump failed on database "bihistory", exiting
That's not good.
First, try per-database dumps. Work out which database has the problem.
Do a:
pg_dumpall -U sns84 --globals-only > globals.sql
then for each database:
pg_dump -U sns84 -f $dbname.sql $dbname
(scripting it if desired), until you see which DB fails to dump. Dump
all the DBs you can successfully dump before proceeding.
Then, in the problem dB, try:
REINDEX pg_catalog.pg_namespace;
does that help?
What's the output of:
SELECT oid, nspname FROM pg_catalog.pg_namespace;
in the problem DB?
What about \dn in psql?
Is all your data for the problem DB in the "public" schema? If so, can
you do a schema-only dump?
pg_dump -U sns84 -n public -f $dbname.dump $dbname
--
Craig Ringer
--
Craig Ringer
^ permalink raw reply [nested|flat] 7+ messages in thread
* Re: Error on pg_dumpall
@ 2012-10-24 18:08 Terry Khatri <terrykhatri531@gmail.com>
parent: Craig Ringer <ringerc@ringerc.id.au>
0 siblings, 0 replies; 7+ messages in thread
From: Terry Khatri @ 2012-10-24 18:08 UTC (permalink / raw)
To: Craig Ringer <ringerc@ringerc.id.au>; +Cc: pgsql-admin
On 23 October 2012 10:15, Craig Ringer <ringerc@ringerc.id.au> wrote:
>
> First, try per-database dumps. Work out which database has the problem.
> Do a:
>
> pg_dumpall -U sns84 --globals-only > globals.sql
>
> then for each database:
>
> pg_dump -U sns84 -f $dbname.sql $dbname
>
> (scripting it if desired), until you see which DB fails to dump. Dump
> all the DBs you can successfully dump before proceeding.
>
Then, in the problem dB, try:
>
> REINDEX pg_catalog.pg_namespace;
>
> does that help?
>
Nope, same problem still - I knew already which db is failing pls see my
initial msg
pg_dump: schema with OID 74363 does not exist
>
What's the output of:
>
> SELECT oid, nspname FROM pg_catalog.pg_namespace;
>
> in the problem DB?
>
nspname
---------
99
11194
11195
11
2200
11459
82537
(7 rows)
That oid does'nt show up here !
List of schemas
Name | Owner
-------------+---------
public | sns84
bihistory | sns84
(2 rows)
>
> Is all your data for the problem DB in the "public" schema? If so, can
> you do a schema-only dump?
>
> pg_dump -U sns84 -n public -f $dbname.dump $dbname
>
No it is in its own schema i.e. bihistory
Please let me know if there's any tweaking that we do in the catalog to fix
it.
Thank you very much for your help
Rgds
T
>
>
>
>
^ permalink raw reply [nested|flat] 7+ messages in thread
end of thread, other threads:[~2012-10-24 18:08 UTC | newest]
Thread overview: 7+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-04-29 13:59 Error on pg_dumpall Carol Walter <walterc@indiana.edu>
2008-04-29 14:37 ` Julian v. Bock <bock@openit.de>
2008-04-29 14:45 ` Tom Lane <tgl@sss.pgh.pa.us>
2008-05-01 14:09 ` Carol Walter <walterc@indiana.edu>
2012-10-21 19:24 Error on pg_dumpall Terry Khatri <terrykhatri531@gmail.com>
2012-10-23 05:15 ` Craig Ringer <ringerc@ringerc.id.au>
2012-10-24 18:08 ` Terry Khatri <terrykhatri531@gmail.com>
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