pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedproblem with pg_dump
5+ messages / 5 participants
[nested] [flat]
* problem with pg_dump
@ 2004-06-13 06:37 pginfo <pginfo@t1.unisoftbg.com>
0 siblings, 0 replies; 5+ messages in thread
From: pginfo @ 2004-06-13 06:37 UTC (permalink / raw)
To: pgsql-admin
Hi all,
We are using pg as db for many erp installations.
In general it is working great.
But at the monet I have problem (I think it is database corrupted, but I
am not sure) by running pg_dump.
I receive this message:
pg_dump acc01 > dmpacc01
pg_dump: query to obtain list of data types failed: ERROR: More than
one tuple returned by a subselect used as an expression.
I can not find nothink wong in my log-file. The lastest records are:
LOG: shutting down
LOG: database system is shut down
LOG: database system was shut down at 2004-06-13 09:39:03 EEST
LOG: checkpoint record is at 3/313382E4
LOG: redo record is at 3/313382E4; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 4046855; next oid: 958527775
LOG: database system is ready
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
WARNING: ROLLBACK: no transaction in progress
ERROR: More than one tuple returned by a subselect used as an expression.
We are using pg 7.3.4 for this install (we will upgrade to 7.4.x soon).
Pls. help me to sort out this problem. It is production db and is
important to resolve the problem.
regards,
ivan.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Problem with pg_dump
@ 2006-03-12 07:56 Sothorn Rordkongthee <rsothorn@yahoo.com>
2006-03-12 08:16 ` Re: Problem with pg_dump Michael Fuhr <mike@fuhr.org>
0 siblings, 1 reply; 5+ messages in thread
From: Sothorn Rordkongthee @ 2006-03-12 07:56 UTC (permalink / raw)
To: pgsql-admin
Problem with pg_dump on PostgreSQL 8.05.
How to solve this problem.
Thank you.
$ pg_dump dbname > 080349.sql
pg_dump: socket not open
pg_dump: SQL command to dump the contents of table
"t_visit_service" failed: PQendcopy() failed.
pg_dump: Error message from server: socket not open
pg_dump: The command was: COPY public.t_visit_service
(t_visit_service_id, t_visit_id, t_patient_id,
assign_date_time, visit_service_staff_doctor,
f_visit_service_status_id, b_service_point_id,
visit_service_treatment_date_time,
visit_service_finish_date_time) TO stdout;
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Problem with pg_dump
2006-03-12 07:56 Problem with pg_dump Sothorn Rordkongthee <rsothorn@yahoo.com>
@ 2006-03-12 08:16 ` Michael Fuhr <mike@fuhr.org>
0 siblings, 0 replies; 5+ messages in thread
From: Michael Fuhr @ 2006-03-12 08:16 UTC (permalink / raw)
To: Sothorn Rordkongthee <rsothorn@yahoo.com>; +Cc: pgsql-admin
On Sat, Mar 11, 2006 at 11:56:55PM -0800, Sothorn Rordkongthee wrote:
> $ pg_dump dbname > 080349.sql
> pg_dump: socket not open
Do you get this error every time you run pg_dump? Do you see any
errors in the server logs?
--
Michael Fuhr
^ permalink raw reply [nested|flat] 5+ messages in thread
* Problem with pg_dump
@ 2009-01-13 21:38 tyrrill_ed@emc.com
2009-01-14 12:04 ` Re: [ADMIN] Problem with pg_dump Emanuel Calvo Franco <postgres.arg@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: tyrrill_ed@emc.com @ 2009-01-13 21:38 UTC (permalink / raw)
To: pgsql-admin
Hi All,
I am a developer of a product that uses a postgresql database (currently
version 8.2.3.1). We dump the database using pg_dumpall. We are
finding data corruption in the dump files about twice a month with a few
thousand installations. I have been able to track down the data
corruption to the original dump file created by pg_dumpall. In every
case I've seen of the corruption 1 or 2 characters are missing. The
problem exhibits itself when loading the dump files. Here is an example
where two lines were combined:
ERROR: extra data after last expected column
CONTEXT: COPY ds_targets, line 42: "1180635517879 3001
C:/SQLBackup/1180635517879 3001 C:/System Volume Information/"
The file bad row was:
1180635517879 3001 C:/SQLBackup/1180635517879 3001 C:/System
Volume Information/
It should have been two rows as follows:
1180635517879 3001 C:/SQLBackup/
1180635517879 3001 C:/System Volume Information/
Is this something that is perhaps fixed in postgresql 8.3? Any
assistance in resolving this problem would be appreciated.
Thanks,
Ed
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [ADMIN] Problem with pg_dump
2009-01-13 21:38 Problem with pg_dump tyrrill_ed@emc.com
@ 2009-01-14 12:04 ` Emanuel Calvo Franco <postgres.arg@gmail.com>
0 siblings, 0 replies; 5+ messages in thread
From: Emanuel Calvo Franco @ 2009-01-14 12:04 UTC (permalink / raw)
To: General PostgreSQL List <pgsql-general@postgresql.org>
2009/1/13 <tyrrill_ed@emc.com>:
> Hi All,
>
>
>
> I am a developer of a product that uses a postgresql database (currently
> version 8.2.3.1). We dump the database using pg_dumpall. We are finding
> data corruption in the dump files about twice a month with a few thousand
> installations. I have been able to track down the data corruption to the
> original dump file created by pg_dumpall. In every case I've seen of the
> corruption 1 or 2 characters are missing. The problem exhibits itself when
> loading the dump files. Here is an example where two lines were combined:
>
>
you try to use pg_dump instead (only the DB you want)?
what fs you are using? (i think is ntfs)
Integrity check?
Force the enconding of dump to the same as OS.
I don't know about a bug in these version, specially in terms of data.
>
> ERROR: extra data after last expected column
>
> CONTEXT: COPY ds_targets, line 42: "1180635517879 3001
> C:/SQLBackup/1180635517879 3001 C:/System Volume Information/"
>
>
>
> The file bad row was:
>
>
>
> 1180635517879 3001 C:/SQLBackup/1180635517879 3001 C:/System
> Volume Information/
>
>
>
> It should have been two rows as follows:
>
>
>
> 1180635517879 3001 C:/SQLBackup/
>
> 1180635517879 3001 C:/System Volume Information/
>
>
>
> Is this something that is perhaps fixed in postgresql 8.3? Any assistance
> in resolving this problem would be appreciated.
>
>
>
> Thanks,
>
> Ed
>
>
>
>
--
Emanuel Calvo Franco
ArPUG / AOSUG Member
Postgresql Support & Admin
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2009-01-14 12:04 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-06-13 06:37 problem with pg_dump pginfo <pginfo@t1.unisoftbg.com>
2006-03-12 07:56 Problem with pg_dump Sothorn Rordkongthee <rsothorn@yahoo.com>
2006-03-12 08:16 ` Re: Problem with pg_dump Michael Fuhr <mike@fuhr.org>
2009-01-13 21:38 Problem with pg_dump tyrrill_ed@emc.com
2009-01-14 12:04 ` Re: [ADMIN] Problem with pg_dump Emanuel Calvo Franco <postgres.arg@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