Re: help getting a backtrace from 9.2 on Ubuntu 13.04? - Mailing list pgsql-general
| From | Chris Curvey |
|---|---|
| Subject | Re: help getting a backtrace from 9.2 on Ubuntu 13.04? |
| Date | |
| Msg-id | EE2174E2DC02564F848D30D14B432D279DC46C04@exchangemb2.local.zuckergoldberg.com Whole thread Raw |
| In response to | Re: help getting a backtrace from 9.2 on Ubuntu 13.04? (Marcin Mańk <marcin.mank@gmail.com>) |
| Responses |
Re: help getting a backtrace from 9.2 on Ubuntu 13.04?
(Adrian Klaver <adrian.klaver@gmail.com>)
Re: help getting a backtrace from 9.2 on Ubuntu 13.04? (Jeff Janes <jeff.janes@gmail.com>) |
| List | pgsql-general |
From: Marcin Mańk [mailto:marcin.mank@gmail.com]
Sent: Monday, September 09, 2013 8:30 PM
To: Chris Curvey
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] help getting a backtrace from 9.2 on Ubuntu 13.04?
On Mon, Sep 9, 2013 at 4:00 PM, Chris Curvey <ccurvey@zuckergoldberg.com> wrote:
But I'm having troubles with the 9.2 server crashing when I'm restoring the dump. I'm using the 9.2 version of pg_dump. I've tried restoring a custom-format dump with pg_restore, and I've tried restoring a text-format dump with pqsl, and both of them are crashing on me.
The data is too sensitive for me to submit a database dump to the community, but I'd like to submit a stack trace, in the hopes that someone might be able to figure out what's going on. But I'm having some trouble getting this done.
Is it crashing on a specific database object? pg_restore -v will tell you how far it went. Then try to restore only that object. Is it perhaps crashing on a specific row?
Try producing a self contained test case (like only the culprit table, anonymized).
Regards
Marcin Mańk
Good advice. I turned on –verbose, and got a ton of output, ending with:
pg_restore: setting owner and privileges for FK CONSTRAINT user_id_refs_id_7ceef80f
pg_restore: setting owner and privileges for FK CONSTRAINT user_id_refs_id_dfbab7d
pg_restore: [archiver (db)] could not execute query: no connection to the server
Command was: -- Completed on 2013-09-09 11:35:16 EDT
pg_restore: [archiver (db)] could not execute query: no connection to the server
Command was: --
-- PostgreSQL database dump complete
–
Which I find really odd, because I specified –no-owner –no-privileges –no-tablespace
chris@mu:/sdb$ pg_restore --dbname=certified_mail_ccc2 --format=c --verbose --clean --no-owner --no-privileges --no-tablespaces -h mu -p 5434 cm_Mon.backup
So now I’m up to three questions. (Why the crash? How to get backtrace? Why are we applying permissions when I said not to?) I guess that’s the nature of the universe. Let me see if I can figure out which table that is and try to create a test case.
Disclaimer
THIS IS A CONFIDENTIAL COMMUNICATION. The information contained in this e-mail is attorney-client privileged and confidential, intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are here by notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by reply e-mail or by telephone (908) 233-8500.Thank you..
pgsql-general by date: