| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mike Wilson <mfwilson(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6733: All Tables Empty After pg_upgrade (PG 9.2.0 beta 2) |
| Date: | 2012-07-15 21:45:28 |
| Message-ID: | 23299.1342388728@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Mike Wilson <mfwilson(at)gmail(dot)com> writes:
> I've had some time to examine this closer over the weekend. It
> appears that pg_upgrade for 9.2b2 segfaults which more than likely has
> something to do with the resulting converted database appearing to
> have no rows.
Yeah, more than likely :-(. Could we see a stack trace from the
segfault?
> Of possible note in this DB is that the previous DBA renamed the
> "postgres" user.
Hmm. There is a known bug in beta2 that's triggered by old and new
clusters not having the same name for the bootstrap superuser; although
I don't recall that the symptoms included a segfault. In any case,
I'd suggest making sure the new cluster is initdb'd under the same
account that currently owns the old cluster.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-07-16 04:53:37 | Re: log_truncate_on_rotation=on is not truncating |
| Previous Message | Noah Misch | 2012-07-15 21:23:44 | Re: BUG #6712: PostgreSQL 9.2 beta2: alter table drop constraint does not work on inherited master table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-07-15 22:37:12 | Re: [PERFORM] DELETE vs TRUNCATE explanation |
| Previous Message | Tom Lane | 2012-07-15 21:36:24 | CompactCheckpointerRequestQueue versus pad bytes |