From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump versus views and opclasses |
Date: | 2009-01-15 22:01:28 |
Message-ID: | 12978.1232056888@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> I recently had pg_dump produce a non-restorable dump for one of my
> databases. I can't share the dump itself, but I can describe what
> went wrong. ...
> * It seems there's no pg_depend entry for
> types/functions/operators/opclasses that the view depends on, unless
> they are part of the SELECT list.
What PG version exactly? We've been moving towards fuller
representation of the semantics in the parse tree over time,
so that's a very relevant question.
FWIW I think this should be pretty much fixed as of CVS HEAD, because
all of the sorting/grouping semantics are now normalized in
SortGroupClauses and find_expr_references() does know about them.
Can you extract a test case from your problem DB so we can verify
nothing got missed?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pasher | 2009-01-15 22:02:09 | Re: Autovacuum daemon terminated by signal 11 |
Previous Message | Josh Berkus | 2009-01-15 21:53:00 | Re: FWD: Re: Updated backslash consistency patch |