Phillip,
> If Tom's not already on top of this, I'd be happy to help. There seem to be
> a few possibilities:
See my last e-mail. I'm not on -bugs, so my responses are delayed by the
moderation process.
> We can remove (3) by just doing a schema-only dump of the original DB. If
> this wor
Tom,
> Do you still have the original database available? The obvious route to
> finding the problem is to watch pg_dump in action and see why it misses
> that view. How do you feel about letting someone else have access to
> your system to do this? (Or get out a debugger and do it yourself..
At 17:21 17/07/2002 -0700, Josh Berkus wrote:
> > We can remove (3) by just doing a schema-only dump of the original DB. If
> > this works, we know it's data related. Ugh.
>
>It's not data related ... the missing object is a view.
I actually meant here that it may be that dumping the data may som
At 13:08 16/07/2002 -0700, Josh Berkus wrote:
>I'd like to work with someone on pinpointing the problem, as obviously this
>could be a critical issue for production databases. However, I'm not sure
>how to submit the files as they are very large (> 90mb) and how can I send
>the original databas
Josh Berkus <[EMAIL PROTECTED]> writes:
> Today I just got done with a very painful restore. PG_dump had failed to back
> up a small view on which 6 other views and functions depended, and I had to
> spend several hours editing the 99mb backup file by hand.
Urgh.
> I'd like to work with someo
Folks,
I am not subscribed to -bugs. Please e-mail me directly.
For some time on 7.2.1 I have suspected that one or two items from large,
complex databases was not getting backed up. However, I could not say
conclusively that this was the case, as it was always possible that I had
missed so
