| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Jamie Fox <jfox(at)directcommerce(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [GENERAL] large object does not exist after pg_migrator |
| Date: | 2009-07-13 22:38:13 |
| Message-ID: | 200907132238.n6DMcDZ08620@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Jamie Fox wrote:
>
> > > I can also see that the pg_largeobject table is different, in the pg_restore
> > > version the Rows (estimated) is 316286 and Rows (counted) is the same, in
> > > the pg_migrator version the Rows (counted) is only 180507.
>
> > Wow, I didn't test large objects specifically, and I am confused why
> > there would be a count discrepancy. I will need to do some research
> > unless someone else can guess about the cause.
>
> Maybe pg_largeobject is not getting frozen?
That would explain the change in count, but I thought we froze
_everything_, and had to.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-13 23:18:09 | Re: [GENERAL] pg_migrator not setting values of sequences? |
| Previous Message | Alvaro Herrera | 2009-07-13 22:35:45 | Re: [GENERAL] large object does not exist after pg_migrator |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mischa Sandberg | 2009-07-13 22:38:36 | Re: Index-only scans |
| Previous Message | Alvaro Herrera | 2009-07-13 22:35:45 | Re: [GENERAL] large object does not exist after pg_migrator |