On Thu, Sep 01, 2005 at 02:59:37PM -0400, Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > I tried the fix mentioned in the earlier message to encourage
> > validation. Now dumping this "fixed" database, and loadinging it into the
> > new database gives:
>
> > ALTER FUNCTION
> > ps
On Thu, Sep 01, 2005 at 02:31:15PM -0400, Tom Lane wrote:
> Patrick Welche <[EMAIL PROTECTED]> writes:
> > I think we still recommend using *new* pg_dump to dump *old* server when
> > upgrading. If one tries that with today's pg_dump (8.1beta1) against
> > a 8.1devel server of 6 May, i.e., predati
Patrick Welche <[EMAIL PROTECTED]> writes:
> I tried the fix mentioned in the earlier message to encourage
> validation. Now dumping this "fixed" database, and loadinging it into the
> new database gives:
> ALTER FUNCTION
> psql:./huge.db:4403: ERROR: function plpgsql_validator(oid) does not exis
Patrick Welche <[EMAIL PROTECTED]> writes:
> I think we still recommend using *new* pg_dump to dump *old* server when
> upgrading. If one tries that with today's pg_dump (8.1beta1) against
> a 8.1devel server of 6 May, i.e., predating roles, one gets:
[ shrug... ] The current code is expecting t
I think we still recommend using *new* pg_dump to dump *old* server when
upgrading. If one tries that with today's pg_dump (8.1beta1) against
a 8.1devel server of 6 May, i.e., predating roles, one gets:
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: relation "pg_catalog.p
