From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Fuhr <mike(at)fuhr(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Neil Conway <neilc(at)samurai(dot)com> |
Subject: | Re: pg_roles: unrecognized token: ":aliasname" |
Date: | 2006-02-23 16:30:27 |
Message-ID: | 22766.1140712227@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Fuhr <mike(at)fuhr(dot)org> writes:
> In an up-to-date HEAD server that was initdb'd on 12 Feb (catalog
> version 200602112):
> test=> SELECT * FROM pg_roles;
> ERROR: unrecognized token: ":aliasname"
> test=> SELECT pg_get_viewdef('pg_roles'::regclass, true);
> ERROR: unrecognized token: ":aliasname"
> This breaks several things, including pg_dump. A newly-initdb'd
> cluster doesn't have the problem. Was something changed that should
> have bumped the catalog version?
Looks like Neil's fault: he changed struct Query on Sunday.
If things are OK after initdb, then it's just a minor faux pas ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Peacetree | 2006-02-23 16:38:48 | Looking for a tool to "*" pg tables as ERDs |
Previous Message | Michael Fuhr | 2006-02-23 16:12:45 | pg_roles: unrecognized token: ":aliasname" |